Beceem Drivers / Licensing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2010-09-28 at 06:30 +0900, Stephen Hemminger wrote: 
> On Mon, 27 Sep 2010 10:47:37 -0700
> Inaky Perez-Gonzalez <inaky at linux.intel.com> wrote:
> 
> > Hi Stephen
> > 
> > 
> > > The driver is a mess, I have a long list of changes that need to be done,
> > > the biggest is that the user space and API model are a mess. It really needs
> > > to be completely rewritten.
> > 
> > Could you do a write up of what is the API model? Additions will be
> > needed to the minimal stack that there is now and I'd like to start
> > thinking about them.
> > 
> > Thanks!
> > 
> 
> The existing code uses a single character device. Read/write are
> control packets, and it has a long list of ioctl's to do things like
> check link status etc.  They also have a binary format configuration
> file that is read in like firmware at the startup.  Much of the configuration
> can probably be eliminated and the rest can either be done as module
> parameters or config fs.

Actually most of the configuration you would want to standarize it under
a common module. I bet it is not that different to what Intel has --
this will be things like setting channel parameters for scanning, etc.

Is the HCI documented in text or just in code?





[Index of Archives]     [Linux Kernel]     [Linux Wireless]     [Linux Bluetooth]     [Linux Netdev]     [Linux Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux