Hi (again!).
Sorry for my first post in french, I didn't realize that most of members are
english-spoken here.
So, for those who don't understand my previous french message, here he is:
I wish to write a driver to make STUSB work under BeOS.
After spending some time to look in depth the differents open sources
available (Linux ones, to date), I still have some technicals questions I
need to clear before starting my project.
Maybe a parallel development (in open source too, of course) can profit to
others plateforms, who know?
I've little to none experience with Linux development, but I've look at many
Linux drivers code to understand how particula hardware works, when better
and more official *datasheets* were lacking.
If it's not the place or time for these questions, a quick reply like "NO"
is expected, at least. ;-)
Okay, here is what I've understand on STUSB Linux official driver internals:
- the box only transmit on ADSL line what he receive from a out USB bulk
endpoint, and transfer what he receive from same ADSL line to the host, via
a in USB bulk endpoint.
Does it support only ATM network? So ,what is the purpose of the MAC address
he *publish* in its serial number USB string descriptor?
- the main job of the driver is the assembly of PPP frames in AAL5 packets,
following PPPoA RFC specifications. Same in other way, he extract PPP frames
from AAL5 packets received. Is it right?
- the SARLib is used to truncate a PPP frame in any AAL5 packet needed, and
reassemble AAL5 packets in single PPP frame. So, who do the PPPoA
encapsulation? The driver code, using SARLib functions for
(un)packetization, or something hidden in Linux kernel, say Linux ATM
module?
> - the firmware aka microcode is upload by the Management application,
> release in binary by Alcatel and must be run before the driver
> initialization. Is this firmware must be upload each time the USB device
> is powering on? No PROM that store it?
>
- In PPPoA specifications, the PPP frames are AAL5 *packetized* directly,
without any modification to PPP frame content? Contrary to PPPoE who need to
modify PPP frame so that PPP compression escape sequences don't break PPPoE
headers recognition. Am I right here?
Thanks for any reply, even an strong "NO!"
Sorry for poor english.
> Philippe Houdoin
> http://philippe.houdoin.free.fr/phil/beos/speed_touch_usb/index-en.html
>
>
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se d�sinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
