uart and puc attach conflict

Kris Kennaway kris at obsecurity.org
Tue Oct 25 12:43:42 PDT 2005


On Tue, Oct 25, 2005 at 11:31:44PM +0400, Gleb Smirnoff wrote:
> On Tue, Oct 25, 2005 at 01:43:37PM -0400, Kris Kennaway wrote:
> K> > I have a problem with  multi-port card based on Nm9845 chip.
> K> > It's a card with 4 com-ports.
> K> > It perfectly works with puc(4) and sio(4) drivers if they compiled into 
> K> > kernel.
> K> > or with puc(4) and uart(4) drivers if they loaded manualy.
> K> > But if puc(4) and uart(4) are compiled into kernel or loaded from
> K> > loader.conf  - problem appears.
> K> 
> K> Isn't puc superceded by uart?  Why do you need both?
> 
> Shouldn't uarts attach on puc? This is what I have in 5.4-STABLE
> system:
> 
> puc0: <Cronyx Omega2-PCI> mem 0xea202000-0xea202fff irq 5 at device 11.0 on pci0
> uart0: <16750 or compatible> on puc0
> uart1: <16750 or compatible> on puc0
> uart2: <16750 or compatible> on puc0
> uart3: <16750 or compatible> on puc0
> uart4: <16750 or compatible> on puc0
> uart5: <16750 or compatible> on puc0
> uart6: <16750 or compatible> on puc0
> uart7: <16750 or compatible> on puc0
> 
> Should it be other way in 6.0 and HEAD?

Sorry, I was confused..you do need both.  I was thinking about uart
superceding other sparc tty drivers.

Kris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20051025/87f3e57d/attachment.bin


More information about the freebsd-current mailing list