> Is USB fs not an auto fs ... ? > I mean as we put the device we get the /dev/<device_id> created auto... > > I can see the /dev/ttyUSB0 entry. If it is auto created then that entry is not required. Another thing that can be tried is using default baudrate of 9600 as below. CONFIG_CMDLINE="rw console=ttyUSB0, 9600 mem =128M" and in inittab ttyUSB0::respawn:/bin/getty -L ttyUSB0 9600 vt102 Regards, Ajay > > Thanks > Prabhu > > On 10/13/08, Gupta, Ajay Kumar <ajay.gupta@xxxxxx> wrote: > > > > > CONFIG_CMDLINE="rw console=ttyUSB0, 115200 mem =128M" > > > > > > and in inittab > > > > > > ttyUSB0::respawn:/bin/getty -L ttyUSB0 115200 vt102 > > > > Apart from this add "mknod /dev/ttyUSB0 c 188 0" in "filesystem/etc/init.d/rcS" > > > > This is required if this node is not created during bootup and usb serial > > device detection. > > > > Regards, > > Ajay > > > > > > > > > --Prabhu > > > > > > On 10/13/08, Prabhu Chawandi <prabhu.chavandi@xxxxxxxxx> wrote: > > > > Some more updates : > > > > > > > > I am using kernel 2.6.12.4. > > > > > > > > It was Tomasz Chmielewski who said that boot messages cant be logged > > > > on USB-serial. soory for the mistake Aristeu Rozanski . > > > > > > > > On 10/13/08, Prabhu Chawandi <prabhu.chavandi@xxxxxxxxx> wrote: > > > > > Hi, > > > > > > > > > > I am not getting any errors .... > > > > > > > > > > I have set the command line parameter. I am booting through CFE , > > > > > This time I am using Serial console while booting I am changing to USB > > > > > serial... > > > > > > > > > > Once the USB -serial driver is loaded I am expecting the rest of the > > > > > logs on the console but I am getting AT command and no more > > > > > messages... > > > > > > > > > > Later I changed inittab file for the login prompt... > > > > > > > > > > I have the other serial connection through which I can control the > > > > > application. When I close that application, through the normal serial, > > > > > I am getting login prompt on both USB-serial and normal Serial. > > > > > > > > > > If I run the application again I am getting logs now on both serials... > > > > > > > > > > I am consfused why I am not getting the boot log messages... > > > > > > > > > > I am sure that I have set commandline parameter properly.... > > > > > > > > > > Aristeu Rozanski has said above that ,,, it is not possoble to log > > > > > boot messages on the USB-serial ... what might be the techincal reason > > > > > ? > > > > > > > > > > Thanks > > > > > Prabhu > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 10/10/08, Greg KH <greg@xxxxxxxxx> wrote: > > > > > > > > > > > > A: No. > > > > > > Q: Should I include quotations after my reply? > > > > > > > > > > > > On Fri, Oct 10, 2008 at 03:28:56PM +0530, Prabhu Chawandi wrote: > > > > > > > On 10/10/08, Prabhu Chawandi <prabhu.chavandi@xxxxxxxxx> wrote: > > > > > > > > Yeah... I did all the configurations. > > > > > > > > > > > > > > > > Still not getting the logs :( > > > > > > > > > > > > > > > > I feel I am missing the part where USB- serial will be registered to > > > > > > > > the tty layer. > > > > > > > > > > > > > > > > or Do I need to insert the code where we will be opening the device > > > > > > > > and performimg the write/read operations. > > > > > > > > > > > > No code needs to be added. > > > > > > > > > > > > Please let us know what errors you are seeing, what does your kernel log > > > > > > messages show, and so on. It should work properly if you tell the boot > > > > > > command line to use the usb-serial port for console messages. > > > > > > > > > > > > thanks, > > > > > > > > > > > > greg k-h > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
