On Tue, 2009-03-31 at 06:29 -0400, Dan Williams wrote: > On Mon, 2009-03-30 at 15:09 -0400, Cody Russell wrote: > > On Mon, 2009-03-30 at 12:01 -0700, Marcel Holtmann wrote: > > > actually you can start by posting lspci or lsusb output (if the > > > ExpressCard using the USB host controller) for you device and see if > > > people can make sense out of it. In case this is connected via USB in > > > the end, then /proc/bus/usb/devices helps a lot, too. > > > > Hi Marcel, > > > > lsusb yields the following line: > > > > Bus 002 Device 004: ID 04e8:6731 Samsung Electronics Co., Ltd > > > > However, /proc/bus/usb/ does not contain "devices". It appears as an > > empty directory. > > It appears that the madwimax project may work with your card: > > http://code.google.com/p/madwimax/source/diff?spec=svn133&r=133&format=side&path=/trunk/src/wimax.c > > http://code.google.com/p/madwimax/ > > I haven't tried the driver, nor is it an "upstream" driver (ie, it's not > in the Linux kernel, thus it's quality isn't widely tested nor is it as > widely reviewed as Intel WiMAX driver). But you might be able to get > *somewhere* with it. Let us know how it goes if you give it a shot. > > Ideally they clean up the driver for inclusion and eventually make it > work using the kernel WiMAX API.
Though, of course, since it's a userspace driver it would have to be re-arranged to be pushed into kernel-land. That might be a good thing if it can share the same API as the Intel cards. Dan _______________________________________________ wimax mailing list [email protected] http://www.linuxwimax.org/mailman/listinfo/wimax
