On Wed, 2005-04-13 at 12:45 +, Paul Slootman wrote:
> Phil Oester <[EMAIL PROTECTED]> wrote:
> >On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
> >> Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
> >> ago) changes the prescaler setting for this device so
On Wed, Apr 13, 2005 at 12:45:51PM +, Paul Slootman wrote:
> We have a variety of Dell rackmount systems, also on Cyclades, and see
> this mess everywhere.
>
> I had reported this problem a little while ago, see
> http://marc.theaimsgroup.com/?l=linux-kernel=111036598927105=2
> but
On Wed, Apr 13, 2005 at 12:45:51PM +, Paul Slootman wrote:
We have a variety of Dell rackmount systems, also on Cyclades, and see
this mess everywhere.
I had reported this problem a little while ago, see
http://marc.theaimsgroup.com/?l=linux-kernelm=111036598927105w=2
but unfortunately
On Wed, 2005-04-13 at 12:45 +, Paul Slootman wrote:
Phil Oester [EMAIL PROTECTED] wrote:
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use
Phil Oester <[EMAIL PROTECTED]> wrote:
>On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
>> Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
>> ago) changes the prescaler setting for this device so we can use the
>> higher speed baud rates. This means any
Phil Oester [EMAIL PROTECTED] wrote:
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use the
higher speed baud rates. This means any programmed
> >
> > Seems like you are correct, given the below patch fixes the garbage
> > output for me.
>
> David,
>
> Is this patch ok for you?
Just an aside, I've had this patch in my own internal tree for over a
year I never thought it would be kernel acceptable... but I noticed
this problem a long
On Mon, Mar 28, 2005 at 09:36:52AM -0800, Phil Oester wrote:
> On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
> > Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
> > ago) changes the prescaler setting for this device so we can use the
> > higher speed baud
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
> Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
> ago) changes the prescaler setting for this device so we can use the
> higher speed baud rates. This means any programmed divisor (programmed
> at early serial
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use the
higher speed baud rates. This means any programmed divisor (programmed
at early serial
On Mon, Mar 28, 2005 at 09:36:52AM -0800, Phil Oester wrote:
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use the
higher speed baud rates. This
Seems like you are correct, given the below patch fixes the garbage
output for me.
David,
Is this patch ok for you?
Just an aside, I've had this patch in my own internal tree for over a
year I never thought it would be kernel acceptable... but I noticed
this problem a long time ago
Hi,
I have come across a 16550A myself (in VMware) and so, tested it.
Linux reports it as a "16550A" while OpenBSD says it's a "NS16550A" --
output to this serial console (vmware: file) works fine, though.
My real box's serial is also a 16550A but havenot tested that- got no cable.
Jan
Hi,
I have come across a 16550A myself (in VMware) and so, tested it.
Linux reports it as a 16550A while OpenBSD says it's a NS16550A --
output to this serial console (vmware: file) works fine, though.
My real box's serial is also a 16550A but havenot tested that- got no cable.
Jan Engelhardt
On Sat, Mar 26, 2005 at 04:37:29PM +, Russell King wrote:
> > serio: i8042 AUX port at 0x60,0x64 irq 12
> > serio: i8042 KBD port at 0x60,0x64 irq 1
> > Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
Garbage here
Sorry -- I was relying upon my (flawed) memory of
On Sat, Mar 26, 2005 at 04:37:29PM +, Russell King wrote:
> > But intererstingly, on identical boxes, the garbage only appears on
> > those hooked up to a PortMaster device - those using a Cyclades never
> > display this problem. (???)
>
> Sorry, I don't understand your scenarios. Can you
On Sat, Mar 26, 2005 at 07:55:49AM -0800, Phil Oester wrote:
> On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
> > Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
> > ago) changes the prescaler setting for this device so we can use the
> > higher speed baud
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
> Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
> ago) changes the prescaler setting for this device so we can use the
> higher speed baud rates. This means any programmed divisor (programmed
> at early serial
On Sat, Mar 26, 2005 at 11:16:09AM +0100, Jan Engelhardt wrote:
> >Well, serial_core seems to think so:
> >
> >Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
> >ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
> >ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
> >ttyS0 at I/O 0x3f8
Il Sat, Mar 26, 2005 at 11:16:09AM +0100, Jan Engelhardt ha scritto:
> >Well, serial_core seems to think so:
> >
> >Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
> >ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
> >ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
> >ttyS0 at I/O
>Well, serial_core seems to think so:
>
>Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
>ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
>ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
>ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
Does it work if you set the baud rate manually, as
Well, serial_core seems to think so:
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
Does it work if you set the baud rate manually, as a
Il Sat, Mar 26, 2005 at 11:16:09AM +0100, Jan Engelhardt ha scritto:
Well, serial_core seems to think so:
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
ttyS0 at I/O 0x3f8 (irq
On Sat, Mar 26, 2005 at 11:16:09AM +0100, Jan Engelhardt wrote:
Well, serial_core seems to think so:
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
ttyS0 at I/O 0x3f8 (irq = 4)
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use the
higher speed baud rates. This means any programmed divisor (programmed
at early serial
On Sat, Mar 26, 2005 at 07:55:49AM -0800, Phil Oester wrote:
On Sat, Mar 26, 2005 at 03:10:05PM +, Russell King wrote:
Doesn't matter. The problem is that dwmw2's NS16550A patch (from ages
ago) changes the prescaler setting for this device so we can use the
higher speed baud rates.
On Sat, Mar 26, 2005 at 04:37:29PM +, Russell King wrote:
But intererstingly, on identical boxes, the garbage only appears on
those hooked up to a PortMaster device - those using a Cyclades never
display this problem. (???)
Sorry, I don't understand your scenarios. Can you explain
On Sat, Mar 26, 2005 at 04:37:29PM +, Russell King wrote:
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
Garbage here
Sorry -- I was relying upon my (flawed) memory of the
Il Fri, Mar 25, 2005 at 08:38:53PM +, Russell King ha scritto:
> On Fri, Mar 25, 2005 at 09:24:15PM +0100, Luca wrote:
> > I attached a null modem cable to my notebook and I'm seeing garbage as
> > soon as the serial driver is loaded. I tried booting with init=/bin/bash
> > to be sure that
On Fri, Mar 25, 2005 at 09:24:15PM +0100, Luca wrote:
> I attached a null modem cable to my notebook and I'm seeing garbage as
> soon as the serial driver is loaded. I tried booting with init=/bin/bash
> to be sure that it's not some rc script doing strange things to the
> serial port, but this
Hi,
I attached a null modem cable to my notebook and I'm seeing garbage as
soon as the serial driver is loaded. I tried booting with init=/bin/bash
to be sure that it's not some rc script doing strange things to the
serial port, but this didn't solve the problem.
This is the relevant part of
On Fri, Mar 25, 2005 at 09:24:15PM +0100, Luca wrote:
I attached a null modem cable to my notebook and I'm seeing garbage as
soon as the serial driver is loaded. I tried booting with init=/bin/bash
to be sure that it's not some rc script doing strange things to the
serial port, but this didn't
Il Fri, Mar 25, 2005 at 08:38:53PM +, Russell King ha scritto:
On Fri, Mar 25, 2005 at 09:24:15PM +0100, Luca wrote:
I attached a null modem cable to my notebook and I'm seeing garbage as
soon as the serial driver is loaded. I tried booting with init=/bin/bash
to be sure that it's not
33 matches
Mail list logo
