Subject: SIIG 4S no go [RE: PCI serial card support?]
To: 'port-macppc@netbsd.org' <port-macppc@netbsd.org>
From: Cliff Neighbors <cliff@allegronetworks.com>
List: port-macppc
Date: 07/06/2000 21:04:56
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BFE7C8.82ADFFE0
Content-Type: text/plain;
charset="iso-8859-1"
I picked up a SIIG 4S PCI 16550-based serial card.
(it's got 2 ports and can be expanded to 4 by populating the 2 empty
sockets).
this card is listed on the netbsd "Machine-independent PCI drivers" page.
I configured the "puc" and "com" drivers:
puc* at pci? dev ? function ?
com* at puc? port ?
and made the kernel....
During kernel start-up, the card is recognized:
puc0 at pci2 dev 3 function 0: SIIG Cyber Serial Dual PCI 16C550A (20x
family)(com, com)
com0 at puc0 port 0: interrupting at irq 53
com0_
underscore indicates cursor position when the system hung.
both "com0..." printf's come from com_puc_attach()\com_puc.c
just before com_attach_subr()\com.c is called.
if this looks familiar to anyone, please let me know.
meanwhile I will try and dig in and see what broke.
hints and advice will be appreciated.
regards,
-cliff-
---
cliff neighbors
allegro networks, inc.
cliff@allegronetworks.com
408-821-5532
---
-----Original Message-----
From: Bill Studenmund [mailto:wrstuden@zembu.com]
Sent: Thursday, July 06, 2000 4:27 PM
To: Cliff Neighbors
Cc: 'port-macppc@netbsd.org'
Subject: Re: PCI serial card support?
On Wed, 5 Jul 2000, Cliff Neighbors wrote:
> I need to add 2 serial lines to my G4 "sawtooth" running netbsd-macppc
> (the 20000606 snapshot). the macppc FAQ mentions USB serial
> support but no mention of PCI serial. PCI serial cards
> are mentioned in the "Machine-independent PCI drivers" page.
>
> Q: can these "universal" comm cards be expected to work OK on
netbsd-macppc?
> comments on favored cards would be helpful.
Kinda. I assume that they show up as "com" devices - normal PC serial
ports?
If so, then they will work.
The problem will be that we don't have terribly good MAKEDEV support.
tty10 will drive one of these serial ports, and you can manually make more
such devices.
I think, though, that we should name the com tty's something other than
tty10 & up. Like ttyC0, ttyC1, etc. - a la port alpha. Thoughgts from the
audience?
Take care,
Bill
------_=_NextPart_001_01BFE7C8.82ADFFE0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>SIIG 4S no go [RE: PCI serial card support?]</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I picked up a SIIG 4S PCI 16550-based serial card.</FONT>
<BR><FONT SIZE=2>(it's got 2 ports and can be expanded to 4 by populating the 2 empty sockets).</FONT>
<BR><FONT SIZE=2>this card is listed on the netbsd "Machine-independent PCI drivers" page.</FONT>
</P>
<P><FONT SIZE=2>I configured the "puc" and "com" drivers:</FONT>
</P>
<P><FONT SIZE=2>puc* at pci? dev ? function ?</FONT>
<BR><FONT SIZE=2>com* at puc? port ?</FONT>
</P>
<P><FONT SIZE=2>and made the kernel....</FONT>
</P>
<BR>
<P><FONT SIZE=2>During kernel start-up, the card is recognized:</FONT>
</P>
<P><FONT SIZE=2>puc0 at pci2 dev 3 function 0: SIIG Cyber Serial Dual PCI 16C550A (20x family)(com, com)</FONT>
<BR><FONT SIZE=2>com0 at puc0 port 0: interrupting at irq 53</FONT>
<BR><FONT SIZE=2>com0_</FONT>
</P>
<P><FONT SIZE=2>underscore indicates cursor position when the system hung. </FONT>
<BR><FONT SIZE=2>both "com0..." printf's come from com_puc_attach()\com_puc.c</FONT>
<BR><FONT SIZE=2>just before com_attach_subr()\com.c is called.</FONT>
</P>
<P><FONT SIZE=2>if this looks familiar to anyone, please let me know.</FONT>
<BR><FONT SIZE=2>meanwhile I will try and dig in and see what broke.</FONT>
<BR><FONT SIZE=2>hints and advice will be appreciated.</FONT>
</P>
<P><FONT SIZE=2>regards,</FONT>
<BR> <FONT SIZE=2>-cliff-</FONT>
</P>
<P><FONT SIZE=2>---</FONT>
<BR><FONT SIZE=2>cliff neighbors</FONT>
<BR><FONT SIZE=2>allegro networks, inc.</FONT>
<BR><FONT SIZE=2>cliff@allegronetworks.com</FONT>
<BR><FONT SIZE=2>408-821-5532</FONT>
<BR><FONT SIZE=2>---</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Bill Studenmund [<A HREF="mailto:wrstuden@zembu.com">mailto:wrstuden@zembu.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Thursday, July 06, 2000 4:27 PM</FONT>
<BR><FONT SIZE=2>To: Cliff Neighbors</FONT>
<BR><FONT SIZE=2>Cc: 'port-macppc@netbsd.org'</FONT>
<BR><FONT SIZE=2>Subject: Re: PCI serial card support?</FONT>
</P>
<BR>
<P><FONT SIZE=2>On Wed, 5 Jul 2000, Cliff Neighbors wrote:</FONT>
</P>
<P><FONT SIZE=2>> I need to add 2 serial lines to my G4 "sawtooth" running netbsd-macppc </FONT>
<BR><FONT SIZE=2>> (the 20000606 snapshot). the macppc FAQ mentions USB serial</FONT>
<BR><FONT SIZE=2>> support but no mention of PCI serial. PCI serial cards</FONT>
<BR><FONT SIZE=2>> are mentioned in the "Machine-independent PCI drivers" page.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Q: can these "universal" comm cards be expected to work OK on netbsd-macppc?</FONT>
<BR><FONT SIZE=2>> comments on favored cards would be helpful.</FONT>
</P>
<P><FONT SIZE=2>Kinda. I assume that they show up as "com" devices - normal PC serial</FONT>
<BR><FONT SIZE=2>ports?</FONT>
</P>
<P><FONT SIZE=2>If so, then they will work.</FONT>
</P>
<P><FONT SIZE=2>The problem will be that we don't have terribly good MAKEDEV support.</FONT>
<BR><FONT SIZE=2>tty10 will drive one of these serial ports, and you can manually make more</FONT>
<BR><FONT SIZE=2>such devices.</FONT>
</P>
<P><FONT SIZE=2>I think, though, that we should name the com tty's something other than</FONT>
<BR><FONT SIZE=2>tty10 & up. Like ttyC0, ttyC1, etc. - a la port alpha. Thoughgts from the</FONT>
<BR><FONT SIZE=2>audience?</FONT>
</P>
<P><FONT SIZE=2>Take care,</FONT>
</P>
<P><FONT SIZE=2>Bill</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BFE7C8.82ADFFE0--