Chinaunix首页 | 论坛 | 博客
  • 博客访问: 239018
  • 博文数量: 68
  • 博客积分: 884
  • 博客等级: 准尉
  • 技术积分: 700
  • 用 户 组: 普通用户
  • 注册时间: 2010-04-25 14:34
文章分类

全部博文(68)

文章存档

2016年(3)

2015年(4)

2014年(9)

2013年(8)

2012年(6)

2011年(19)

2010年(19)

我的朋友

分类:

2011-03-06 13:31:02

The harvest day.
Two issues gone, i have a relaxed weekend!
 
1.Voip
Refrence to Forrest's config files of DHCP & DNS, change them for suitable with my own env.
But i still do not know what's the root issue. Maybe the key point is settings in CM.
Yeah, i reset CM's emtaConfigVoice config to default. And it works!!! So excited!!!
Next monday i'll debug to locate the root issue.~~
 
2. 821N V3 Wireless driver.
It confused me so long ,at lease 2 weeks.So sick TP-Link is!!!
According to linux-wireless supported device list, 821N Ver 2.0 will be supported without any drivers porting, but only enable it in kernel config! AR9271 chipset is inside!
But, i'm so sad while it arrived!The card is updated to Ver 3.0, with AR7010(said plus AR9287) instead of. That's not supported by 2.6.31 Kernel.
I could not find any offical note for this update, however the same product number on them.f00k!
I have to porting the latest compat-wireless driver to my kernel.in fact, it's indeed not difficult, the only things is config, compiling, compiling compiling...., exclude patch the led-class driver--i remove it!Go well, the final problem is firmware could not be download, don't know why..So sad! Yesterday night i found some manuals in Kernel Documents folder,fortunately, there is a detail introduce of firmware download. Yeah, i see. I missing the hotplug-firmware-download script.I wrote a shell script executed by manual while plugin, transfered needed firmware from userspace to kernel.Hehe, it works well!!Issue gone!
 
 
From kernel document :

 request_firmware() hotplug interface:
 ------------------------------------
 Copyright (C) 2003 Manuel Estrada Sainz
 
........
 High level behavior (mixed):
 ============================
 kernel(driver): calls request_firmware(&fw_entry, $FIRMWARE, device)
 userspace:
  - /sys/class/firmware/xxx/{loading,data} appear.
 - hotplug gets called with a firmware identifier in $FIRMWARE
   and the usual hotplug environment.
  - hotplug: echo 1 > /sys/class/firmware/xxx/loading
 kernel: Discard any previous partial load.
 userspace:
  - hotplug: cat appropriate_firmware_image > \
     /sys/class/firmware/xxx/data
 kernel: grows a buffer in PAGE_SIZE increments to hold the image as it
  comes in.
 userspace:
  - hotplug: echo 0 > /sys/class/firmware/xxx/loading
 kernel: request_firmware() returns and the driver has the firmware
  image in fw_entry->{data,size}. If something went wrong
  request_firmware() returns non-zero and fw_entry is set to
  NULL.
 kernel(driver): Driver code calls release_firmware(fw_entry) releasing
   the firmware image and any related resource.
阅读(1840) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~