Dell LAtitude PCMCIA adapter
I have run across a problem with 2.4.3 on my Dell lattitude CPx. It boots ok but when it gets to bringing up the pcmcia adapter it gets a spurious interrupt from the pcmcia socket and then fials to init. This is the last problem (apart from NFS.lockd) that I am having. If anyone has any insight into this, I am not really up on pcmcia sockets, etc... I would appreciate it Marc Karasek Sr. Firmware Engineer iVivity Inc. [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
FW: Bug in serial.c
-Original Message- From: Marc Karasek To: 'Disconnect ' Sent: 4/19/01 11:49 AM Subject: RE: Bug in serial.c I have changed everything to point to /dev/ttyS0. The settings in lilo.conf (I am booting from a floppy to emulate the embedded space) are all for ttyS0. Lilo pritns to the terminal (minicom on another Linux box) and the kernel prints as well. When I get to inittab (running busybox) it asks for some input thru a script to setup the embedded emulation. At this point it just sits there. If I turn on the debug in serial.c I can see the characters (hex values) as I type. Kernel 2.4.2 works fine, with the only problem being the smp compile issue. As I need module support and cannot have a kernel of 600k+ size I am in a bit of a pickle. -Original Message- From: Disconnect To: Marc Karasek Cc: '[EMAIL PROTECTED]' Sent: 4/19/01 11:38 AM Subject: Re: Bug in serial.c On Thu, 19 Apr 2001, Marc Karasek did have cause to say: > 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the > terminal but when you get to a point of entering data (login, configuration > scripts, etc) the terminal does not accept any input. Most gettys and such take a /dev/tty* argument, which has to be changed to point to the serial port for a serial console. Config scripts (and anything else) specifically using /dev/tty or /dev/console should work fine, however. (I wouldn't recommend pointing a getty at /dev/console - we had some issues on a headless server trying that. Easiest to point it at /dev/ttyS0 or whatnot.) > > So far I have been able to debug to the point where I see that the kernel is > receiving the characters from the serial.c driver. But it never echos them > or does anything else with them. I will continue to look into this at this > end. > > I was also wondering if anyone else has seen this or if a patch is avail for > this bug?? > > Marc Karasek > Sr. Firmware Engineer > iVivity Inc > [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ --- _.-==-._ | [EMAIL PROTECTED]| And Remember... \ [EMAIL PROTECTED] / He who controls Purple controls the Universe.. PGP Key given on Request Or at least the Purple parts! -BEGIN GEEK CODE BLOCK- Version: 3.1 [www.ebb.org/ungeek] GIT/CC/CM/AT d--(-)@ s+:-- a-->? C$ ULBS*$ P+>+++ L>+ E--- W+++ N+@ o+>$ K? w--->+ O- M V-- PS+() PE Y+@ PGP++() t 5--- X-- R tv+@ b>$ DI D++(+++) G++ e* h(-)* r++ y++ --END GEEK CODE BLOCK-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
FW: Bug in serial.c
-Original Message- From: Marc Karasek To: 'Richard B. Johnson ' Sent: 4/19/01 11:53 AM Subject: RE: Bug in serial.c Did something change between 2.4.2 & 2.4.3? Under 2.4.2 I did not have to init the terminal (are you refering to the host or client side?) and just accepted the defaults (9600, 8n1) which was fine for debug and terminal I/O. My issue is with 2.4.2 it works with 2.4.3 (same .config) it does not. So in my mind this is a bug of some type. :-) Which kernel are you using in your embedded project?? -Original Message- From: Richard B. Johnson To: Marc Karasek Cc: '[EMAIL PROTECTED]' Sent: 4/19/01 11:43 AM Subject: Re: Bug in serial.c On Thu, 19 Apr 2001, Marc Karasek wrote: > I am doing some embedded development with the 2.4.x series and have noticed > a few things.. > [SNIPPED...] > > 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the > terminal but when you get to a point of entering data (login, configuration > scripts, etc) the terminal does not accept any input. > It is not broken. It is used all the while in our embeded systems. > So far I have been able to debug to the point where I see that the kernel is > receiving the characters from the serial.c driver. But it never echos them > or does anything else with them. I will continue to look into this at this > end. > Did you ever initialize the terminal? And I'm not talking about baud-rate. There is a termios structure of information necessary to configure a terminal for I/O. > I was also wondering if anyone else has seen this or if a patch is avail for > this bug?? You refer to a BUG? There isn't any of the kind you describe. Cheers, Dick Johnson Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips). "Memory is like gasoline. You use it up when you are running. Of course you get it all back when you reboot..."; Actual explanation obtained from the Micro$oft help desk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Bug in serial.c
I am doing some embedded development with the 2.4.x series and have noticed a few things.. 1) In 2.4.2 in order to compile with module support you also had to turn on smp support. This has been fixed in the 2.4.3 release. This bloated the kernel image to 600k+ which in an embedded world is not a good thing :-) 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the terminal but when you get to a point of entering data (login, configuration scripts, etc) the terminal does not accept any input. So far I have been able to debug to the point where I see that the kernel is receiving the characters from the serial.c driver. But it never echos them or does anything else with them. I will continue to look into this at this end. I was also wondering if anyone else has seen this or if a patch is avail for this bug?? Marc Karasek Sr. Firmware Engineer iVivity Inc [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
