question regarding 2.6.16.24,

question regarding 2.6.16.24,

[Thomas L. Marshall]

I am currently using usb-serial devices (pcmcia cellular CDMA cards) with no
problem. I am, however, not having the same success with the serial_cs
driver (PCMCIA modems (Zoom v92 and GSM devices).  Based on my success
seeing the ttyUSB devices, I had held out great hopes that the same would be
true for serial_cs devices as well.

I am using a static 2.6.16.24 kernel (CONFIG_MODULES not set) and I am
currently trying to digest the details pcmciautils, sysfsutils, possibly
udev, and hotplug.

Is it possible to avoid the userspace interface altogether?  (Static kernel,
pcmcia and serial_cs configured with the necessary manufacturer/product ids
added to the serial_cs id_table)

If so, is my lack of success related to the pci/pcmcia devices I am using?
(lspci returns 00:0a.0, 00:0a.1 for the two Yenta sockets).

I would really appreciate any suggestions that would help me find the
correct path through this problem.  Even a pointer to some documentation
that would help me understand the kernel process that establishes a link to
the tty device (presumably /dev/ttyS*) from the socket_insert event being
sent (drivers/pcmcia/cs.c).

Thank you very much,

Tom



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: question regarding 2.6.16.24,

[Thomas L. Marshall]

OK nevermine (but thank you very much anyway), I think that I have all of my
issues figured out...

I needed to set up the "resource database".  In the end, I did by echoing
the resource ranges to
/sys/class/pcmcia_socket/*/available_resource_{io,mem}.  I didn't understand
the documentation on this very well.

Additionally, I needed to add support for these devices to the driver,
serial_cs.c so they would be recognized without the additional utilities.

Ultimately, I was able to trace the pcmcia driver code from socket
registration through device configuration.  I will be happy to share the
details if anyone is interested.  The real magic for me was understanding
the macros in include/pcmcia/devide_id.h and the id_tables in the driver
code as well as the "resource database" which is essentially the
registration of available resources (io and memory ranges typically found in
/etc/pcmcia/config.opts) by using the
/sys/class/pcmcia_socket/*/available_resource_* interfaces.

Tom

-----Original Message-----
From: linux-hotplug-devel-bounces@lists.sourceforge.net
[mailto:linux-hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of
Thomas L. Marshall
Sent: Saturday, August 19, 2006 12:19 PM
To: linux-hotplug-devel@lists.sourceforge.net
Subject: question regarding 2.6.16.24,serial_cs and generic pcmcia modems
(zoom v92, etc)

I am currently using usb-serial devices (pcmcia cellular CDMA cards) with no
problem. I am, however, not having the same success with the serial_cs
driver (PCMCIA modems (Zoom v92 and GSM devices).  Based on my success
seeing the ttyUSB devices, I had held out great hopes that the same would be
true for serial_cs devices as well.

I am using a static 2.6.16.24 kernel (CONFIG_MODULES not set) and I am
currently trying to digest the details pcmciautils, sysfsutils, possibly
udev, and hotplug.

Is it possible to avoid the userspace interface altogether?  (Static kernel,
pcmcia and serial_cs configured with the necessary manufacturer/product ids
added to the serial_cs id_table)

If so, is my lack of success related to the pci/pcmcia devices I am using?
(lspci returns 00:0a.0, 00:0a.1 for the two Yenta sockets).

I would really appreciate any suggestions that would help me find the
correct path through this problem.  Even a pointer to some documentation
that would help me understand the kernel process that establishes a link to
the tty device (presumably /dev/ttyS*) from the socket_insert event being
sent (drivers/pcmcia/cs.c).

Thank you very much,

Tom



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel