On Tue, Feb 27, 2007 at 03:40:57PM -0500, Rob Prowel wrote:
> Stuart MacDonald wrote:
> >Would it be more intuitive to give ports the default uartclk of
> >1843200 at init time? That would avoid this issue, but would make the
> >baud rates come out wrong on hardware with a non-standard clock, if a
Stuart MacDonald wrote:
Would it be more intuitive to give ports the default uartclk of
1843200 at init time? That would avoid this issue, but would make the
baud rates come out wrong on hardware with a non-standard clock, if a
base baud wasn't specified.
I prefer the option to specify the
From: Russell King [mailto:[EMAIL PROTECTED]
> After experimenting here, it turns out the reason is you're trying to
> configure a port with a zero base baud. Unfortunately, it starts off
> as zero.
That explains why adding the fourport module fixed Rob's issue, as the
fourport code sets a uartcl
On Tue, Feb 27, 2007 at 09:24:32AM -0500, Rob Prowel wrote:
> Russell King wrote:
> >On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote:
> >
> >>See below for a (script) dump of that demonstrates the behavior I
> >>describe. Additional ports are not configurable until a driver such as
Russell King wrote:
On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote:
See below for a (script) dump of that demonstrates the behavior I
describe. Additional ports are not configurable until a driver such as
fourport is loaded. This is in 2.6.20.1 and 2.6.17 (those versions I
hav
On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote:
> See below for a (script) dump of that demonstrates the behavior I
> describe. Additional ports are not configurable until a driver such as
> fourport is loaded. This is in 2.6.20.1 and 2.6.17 (those versions I
> have tested).
Check
Stuart MacDonald wrote:
I use the options below:
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=32
This makes the internal table be 32 ports big. The first four ports
end up configured for legacy/standard com ports, the rest are
unco
From: On Behalf Of Rob Prowel
> Russell King wrote:
> > You don't even need to do that. Just configure SERIAL_8250_NR_UARTS
> > and SERIAL_8250_RUNTIME_UARTS appropriately for your
> system. There's
> > absolutely no need to build any of the additional modules.
> >
> Unfortunately what I'm se
Thanks so much for your followup.
Russell King wrote:
On Fri, Feb 23, 2007 at 12:05:48PM -0500, Rob Prowel wrote:
At least now, with fourport compiled into the kernel,
You don't even need to do that. Just configure SERIAL_8250_NR_UARTS
and SERIAL_8250_RUNTIME_UARTS appropriately for
On Fri, Feb 23, 2007 at 12:05:48PM -0500, Rob Prowel wrote:
> At least now, with fourport compiled into the kernel,
You don't even need to do that. Just configure SERIAL_8250_NR_UARTS
and SERIAL_8250_RUNTIME_UARTS appropriately for your system. There's
absolutely no need to build any of the addi
I have a PC104 embedded system and am trying to make a Diamond
Emerald-mm-opto four port serial board work in a recent kernel version
(>=2.6.17). The vendor only validates the board against 2.6.11: a
kernel nearly two years old and several serial kernel config parameters
have changed in that t
11 matches
Mail list logo
