On Wed, Feb 14, 2007 at 05:39:22PM -0700, [EMAIL PROTECTED] wrote:
> Well, this is the most bastardized sucker I've ever seen. . . I have had
> no end of trouble with it (couldn't even get a boot loader to work with
> it - had to write my own). And, as luck would have it, the serial port
> is no
On Wed, Feb 14, 2007 at 05:39:22PM -0700, [EMAIL PROTECTED] wrote:
Well, this is the most bastardized sucker I've ever seen. . . I have had
no end of trouble with it (couldn't even get a boot loader to work with
it - had to write my own). And, as luck would have it, the serial port
is no
> > In a previous post I incorrectly stated that my serial port is a
> > TI16750, as this is what /proc/tty/... revealed to me. After
> > re-reading the product manual, I see that this is actually a 16550.
> > Since Linux is seeing this port as a 16750, could that explain why I'm
> > seeing
On Wed, 14 Feb 2007 16:11:14 -0700
[EMAIL PROTECTED] wrote:
> In a previous post I incorrectly stated that my serial port is a
> TI16750, as this is what /proc/tty/... revealed to me. After
> re-reading the product manual, I see that this is actually a 16550.
> Since Linux is seeing this port
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a 16750, could that explain why I'm
seeing missing characters in
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a 16750, could that explain why I'm
seeing missing characters in
On Wed, 14 Feb 2007 16:11:14 -0700
[EMAIL PROTECTED] wrote:
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a 16750, could that explain why I'm
seeing missing
David Lang wrote:
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already
seen this -- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
David Lang wrote:
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already
seen this -- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already seen this
-- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
System: VersaLogic
For those of you who are on BusyBox's mailing list, you've already seen
this -- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
System: VersaLogic 568 (STD80/STD32 Bus, i386 based computer)
For those of you who are on BusyBox's mailing list, you've already seen
this -- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
System: VersaLogic 568 (STD80/STD32 Bus, i386 based computer)
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already seen this
-- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
System: VersaLogic
14 matches
Mail list logo
