List Info

Thread: puc based 16550 on macppc?
puc based 16550 on macppc?
user name
 2007-04-17 14:00:27 
Hello, I'm trying to get a Lava DSerial PCI card to work on
my B&W G3.
 I did get the card to work on a i386 box (4.0_BETA) by
adding some
lines to pucdata.c.

However, on 3.1 macppc, I get:

puc0 at pci1 dev 2 function 0: Lava Computers new serial
(com, com)
puc0: couldn't map BAR at offset 0x10
puc0: couldn't map BAR at offset 0x14
pci_intr_map: no mapping for pin C
puc0: couldn't map interrupt

("Lava Computers new serial" Is what I entered
into pucdata.c...)

Following is the pcictl dump; unfortunately, I do not
understand the
pci magics all that well... anyone here has experience with
puc-attached serial ports?

Is there any way to make OF know about the ports? (It'd be
nice to get
console on that but it's not critical... I'd just like to
make the
port work normally.)

Any ideas?
Joe.

-bash-3.2$ pcictl /dev/pci1 dump -d 2
PCI configuration registers:
  Common header:
    0x00: 0x02001407 0x04800040 0x07000300 0x00000000

    Vendor Name: Lava Semiconductor Manufacturing (0x1407)
    Device ID: 0x0200
    Command register: 0x0040
      I/O space accesses: off
      Memory space accesses: off
      Bus mastering: off
      Special cycles: off
      MWI transactions: off
      Palette snooping: off
      Parity error checking: on
      Address/data stepping: off
      System error (SERR): off
      Fast back-to-back transactions: off
    Status register: 0x0480
      Capability List support: off
      66 MHz capable: off
      User Definable Features (UDF) support: off
      Fast back-to-back capable: on
      Data parity error detected: off
      DEVSEL timing: slow (0x2)
      Slave signaled Target Abort: off
      Master received Target Abort: off
      Master received Master Abort: off
      Asserted System Error (SERR): off
      Parity error detected: off
    Class Name: communications (0x07)
    Subclass Name: serial (0x00)
    Interface: 0x03
    Revision ID: 0x00
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x00
    Cache Line Size: 0x00

  Type 0 ("normal" device) header:
    0x10: 0x0000fff9 0x0000fff9 0x00000000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0x02001407
    0x30: 0x00000000 0x00000000 0x00000000 0x00000100

    Base address register at 0x10
      type: i/o
      base: 0x0000fff8, not sized
    Base address register at 0x14
      type: i/o
      base: 0x0000fff8, not sized
    Base address register at 0x18
      not implemented(?)
    Base address register at 0x1c
      not implemented(?)
    Base address register at 0x20
      not implemented(?)
    Base address register at 0x24
      not implemented(?)
    Cardbus CIS Pointer: 0x00000000
    Subsystem vendor ID: 0x1407
    Subsystem ID: 0x0200
    Expansion ROM Base Address: 0x00000000
    Reserved  0x34: 0x00000000
    Reserved  0x38: 0x00000000
    Maximum Latency: 0x00
    Minimum Grant: 0x00
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x00

  Device-dependent header:
    0x40: 0x00000000 0x00000000 0x00000000 0x00000000
    0x50: 0x00000000 0x00000000 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

-bash-3.2$
Re: puc based 16550 on macppc?
country flaguser name
United States		 2007-04-17 14:27:09 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Apr 17, 2007, at 15:00, Joachim Thiemann wrote:

> Hello, I'm trying to get a Lava DSerial PCI card to
work on my B&W G3.
> I did get the card to work on a i386 box (4.0_BETA) by
adding some
> lines to pucdata.c.
>
> However, on 3.1 macppc, I get:
>
> puc0 at pci1 dev 2 function 0: Lava Computers new
serial (com, com)
> puc0: couldn't map BAR at offset 0x10
> puc0: couldn't map BAR at offset 0x14

>    Base address register at 0x10
>      type: i/o
>      base: 0x0000fff8, not sized
>    Base address register at 0x14
>      type: i/o
>      base: 0x0000fff8, not sized

Those BARs overlap and contain bogus. Looks like they
weren't 
configured by OF for some reason.

> pci_intr_map: no mapping for pin C
> puc0: couldn't map interrupt

>    Interrupt line: 0x00

and this is bogus too.

> Is there any way to make OF know about the ports?

Not really, unless you write an fcode driver for it.

> (It'd be nice to get console on that but it's not
critical... I'd just 
> like to make the
> port work normally.)

The card looks unconfigured - does it show up in OF's device
tree at 
all?

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRiUfjcpnzkX8Yg2nAQLazAf+OKBgfDmxosy3J9tFgRoCaeWcAtb4
An99
axSoyqQ8TWBEvHoP2y8jS7Trtu5Kv8x1+AOdHzYydssVBQd4qt+8CAXs6WKx
C1XD
xLiMIjCNu6jadvobKI+FzzIHEbjL2Txn8uNkLesFXGhZBFJdVJBhbyRI30lp
dzgi
S72fAh9qVJQvI2Z39rCC0xiuwd3hH7QWkMFvEq0D9rM9ipGdUoMGAzo2gEba
1C90
zg1U4MYLCGoIEloAWpYTpwVjHCjtRKZ2XDcOH7eJBTitTfelQW4lrkWWyOLB
BvJM
JOhBHk52cPfWIAz2yOvvQQwdGjGJYChxLlkL8qlCW1yf6T5YFvm7Xw==
=Mnlc
-----END PGP SIGNATURE-----
Re: puc based 16550 on macppc?
user name
 2007-04-17 16:46:09 
On 17/04/07, Michael Lorenz <macallannetbsd.org> wrote:
> On Apr 17, 2007, at 15:00, Joachim Thiemann wrote:
> > puc0 at pci1 dev 2 function 0: Lava Computers new
serial (com, com)
> > puc0: couldn't map BAR at offset 0x10
> > puc0: couldn't map BAR at offset 0x14
>
> >    Base address register at 0x10
> >      type: i/o
> >      base: 0x0000fff8, not sized
> >    Base address register at 0x14
> >      type: i/o
> >      base: 0x0000fff8, not sized
>
> Those BARs overlap and contain bogus. Looks like they
weren't
> configured by OF for some reason.
>
> > pci_intr_map: no mapping for pin C
> > puc0: couldn't map interrupt
>
> >    Interrupt line: 0x00
>
> and this is bogus too.

> The card looks unconfigured - does it show up in OF's
device tree at
> all?

Hi Michael, thanks for your help.

First off, if I go to OF, then do dev /pci, then ls I get

ff85faf0   /pci-bridged
... bunch of stuff...
ff87ab28      /pci 1407,200d

I guess OF at least sees the card, but doesn't do anthing
about it.
Is there anything else I can get out of OF?

I notice Valeriy is using 4.99.9 - does current do anything
different
during the bus initialisation?  I'd rather stay with a
stable release
though, this is my home server...
(I tried a 4.0_BETA kernel, and got the same message)

Joe.
Re: puc based 16550 on macppc?
country flaguser name
United States		 2007-04-17 17:15:38 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Apr 17, 2007, at 17:46, Joachim Thiemann wrote:

> On 17/04/07, Michael Lorenz <macallannetbsd.org> wrote:
>> On Apr 17, 2007, at 15:00, Joachim Thiemann wrote:
>> > puc0 at pci1 dev 2 function 0: Lava Computers
new serial (com, com)
>> > puc0: couldn't map BAR at offset 0x10
>> > puc0: couldn't map BAR at offset 0x14
>>
>> >    Base address register at 0x10
>> >      type: i/o
>> >      base: 0x0000fff8, not sized
>> >    Base address register at 0x14
>> >      type: i/o
>> >      base: 0x0000fff8, not sized
>>
>> Those BARs overlap and contain bogus. Looks like
they weren't
>> configured by OF for some reason.
>>
>> > pci_intr_map: no mapping for pin C
>> > puc0: couldn't map interrupt
>>
>> >    Interrupt line: 0x00
>>
>> and this is bogus too.
>
>> The card looks unconfigured - does it show up in
OF's device tree at
>> all?
>
> Hi Michael, thanks for your help.
>
> First off, if I go to OF, then do dev /pci, then ls I
get
>
> ff85faf0   /pci-bridged
> ... bunch of stuff...
> ff87ab28      /pci 1407,200d
>
> I guess OF at least sees the card, but doesn't do
anthing about it.
> Is there anything else I can get out of OF?

Maybe - please run ofctl -p ( this will dump the OF tree
including 
properties ) and post the relevant part ( or the whole thing
if you're 
unsure )

> I notice Valeriy is using 4.99.9 - does current do
anything different
> during the bus initialisation?

Nothing that should affect your card. All I changed lately
was about 
proper ( or rather - less broken ) setup of CardBus
bridges.

> I'd rather stay with a stable release though, this is
my home server...
> (I tried a 4.0_BETA kernel, and got the same message)

The problem is likely with OF, not NetBSD. On macppc NetBSD
doesn't do 
much in terms of PCI bus configuration - basically it walks
the tree OF 
tree and fixes some known weirdnesses but nothing more. It
will not 
attempt to configure any PCI device that OF didn't set up.
Maybe OF put something into device properties and for some
reason 
failed to program the card's config space - if that's the
case I can 
likely fix it.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRiVHCspnzkX8Yg2nAQLCQgf+Pa6OM/SMIybNmnonsKaKCVUL3JBl
h4F1
hjOl2SK7wGl8+6SOQscpjAZrli8Fujs/55dFF8OJaW/f3OkC5A8YuK43MUvw
dVtL
iVI78+YyHIQI6Mllza1E8iq+JyBsfWQMgvF/0eq6ksXZsWHaljChVUjHGj2q
Q9fA
EuYvjgWrVVPlrN00GXCRqogn+0oJvO9xtDBMz5gR21EonqZzdSWXh0sf2RLy
Skt5
76ZOqodi6wKbqqUCICOog1/e+PYIt4g73ygbl2WQDCOUHKgIoOCJKZhGLCF2
FEhL
I3Zf+n391qrWqxkQwSdvjNvqkeo8eg0LrAJNs/f0Eh9obMG/nreTwg==
=GSS4
-----END PGP SIGNATURE-----
Re: puc based 16550 on macppc?
user name
 2007-04-17 18:16:05 
On 17/04/07, Michael Lorenz <macallannetbsd.org> wrote:
> Maybe - please run ofctl -p ( this will dump the OF
tree including
> properties ) and post the relevant part ( or the whole
thing if you're
> unsure )

No prob, though ofctl is not in 3.1, I just compiled ofctl.c
from
-current.  I assume the result is not affected, though:

ff87ab28: /pci80000000/pci-bridged/pci1407,2002

vendor-id               00001407 ........ ........ ........ 
 ....
device-id               00000200 ........ ........ ........ 
 ....
revision-id             00000000 ........ ........ ........ 
 ....
class-code              00070003 ........ ........ ........ 
 ....
interrupts              00000001 ........ ........ ........ 
 ....
min-grant               00000000 ........ ........ ........ 
 ....
max-latency             00000000 ........ ........ ........ 
 ....
subsystem-vendor-id     00001407 ........ ........ ........ 
 ....
subsystem-id            00000200 ........ ........ ........ 
 ....
devsel-speed            00000002 ........ ........ ........ 
 ....
fast-back-to-back
name                    70636931 3430372c 32303000 ........ 
 "pci1407,200"
compatible              70636931 3430372c 32303000 ........ 
 "pci1407,200"
            000c:       70636931 3430372c 32303000 ........ 
 "pci1407,200"
            0018:       70636963 6c617373 2c303730 30303300 
 "pciclass,070003"
reg                     00011000 00000000 00000000 00000000 
 ................
            0010:       00000000 21011010 00000000 00000000 
 ....!...........
            0020:       00000000 00000010 21011014 00000000 
 ........!.......
            0030:       00000000 00000000 00000010 ........ 
 ............
assigned-addresses

> Maybe OF put something into device properties and for
some reason
> failed to program the card's config space - if that's
the case I can
> likely fix it.

Your efforts are greatly appreciated  Do you
need the changes to
pucdata.c?  I already submitted a pr but can't seem to find
it anymore
(??? I am _sure_ I submitted a pr, but can't even see it
the
netbsd-bugs archive. Strange.)

Anyways, it's simply
        /* Lava Computers new serial */
        {   "Lava Computers new serial",
            {   0x1407, 0x0200, 0,      0       },
            {   0xffff, 0xfffc, 0,      0       },
            {
                { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ*4
},
                { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ*4
},
            },
        },

The COM_FREQ multiplier was found "empirically"


Joe.
Re: puc based 16550 on macppc?
country flaguser name
United States		 2007-04-17 23:51:52 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Apr 17, 2007, at 19:16, Joachim Thiemann wrote:

> On 17/04/07, Michael Lorenz <macallannetbsd.org> wrote:
>> Maybe - please run ofctl -p ( this will dump the OF
tree including
>> properties ) and post the relevant part ( or the
whole thing if you're
>> unsure )
>
> No prob, though ofctl is not in 3.1, I just compiled
ofctl.c from
> -current.  I assume the result is not affected,
though:

Nope, same thing. The OF interface hasn't changed in ages.

> ff87ab28: /pci80000000/pci-bridged/pci1407,2002
>
> vendor-id               00001407 ........ ........
........   ....
> device-id               00000200 ........ ........
........   ....
> revision-id             00000000 ........ ........
........   ....
> class-code              00070003 ........ ........
........   ....
> interrupts              00000001 ........ ........
........   ....
> min-grant               00000000 ........ ........
........   ....
> max-latency             00000000 ........ ........
........   ....
> subsystem-vendor-id     00001407 ........ ........
........   ....
> subsystem-id            00000200 ........ ........
........   ....
> devsel-speed            00000002 ........ ........
........   ....
> fast-back-to-back
> name                    70636931 3430372c 32303000
........   
> "pci1407,200"
> compatible              70636931 3430372c 32303000
........   
> "pci1407,200"
>            000c:       70636931 3430372c 32303000
........   
> "pci1407,200"
>            0018:       70636963 6c617373 2c303730
30303300   
> "pciclass,070003"
> reg                     00011000 00000000 00000000
00000000   
> ................
>            0010:       00000000 21011010 00000000
00000000   
> ....!...........
>            0020:       00000000 00000010 21011014
00000000   
> ........!.......
>            0030:       00000000 00000000 00000010
........   
> ............
> assigned-addresses

Hmm, so OF did try to set up something. The reg property
looks weird 
though.

>> Maybe OF put something into device properties and
for some reason
>> failed to program the card's config space - if
that's the case I can
>> likely fix it.
>
> Your efforts are greatly appreciated  Do you
need the changes to
> pucdata.c?  I already submitted a pr but can't seem to
find it anymore
> (??? I am _sure_ I submitted a pr, but can't even see
it the
> netbsd-bugs archive. Strange.)
>
> Anyways, it's simply
>        /* Lava Computers new serial */
>        {   "Lava Computers new serial",
>            {   0x1407, 0x0200, 0,      0       },
>            {   0xffff, 0xfffc, 0,      0       },
>            {
>                { PUC_PORT_TYPE_COM, 0x10, 0x00,
COM_FREQ*4 },
>                { PUC_PORT_TYPE_COM, 0x14, 0x00,
COM_FREQ*4 },
>            },
>        },
>
> The COM_FREQ multiplier was found
"empirically" 

Looks like I'll need to look at the puc code - I have no
idea what this 
code does ;)
One final thing to test though - could you please build a
kernel 
without the puc driver and check if the card's config space
looks any 
different?

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRiWj6MpnzkX8Yg2nAQJZKAf/W/nae2Tm10UF5ywFfwY9fCbdUYyK
0Jxo
4vqHrDK8a+FHdApEocKI7D7Mr6iXX9CRtn1+xGOuSTD24kVQmAiL12/TmmQ5
b98C
ZxVXeMp4GDQvDICEhQhNGOShNq4kUA7xdOmY091sgrHUzTriHR9CVaLjMD9B
1fWS
Vnz/afkhJ+M3giIhkBD9A/DRyKSEe9Xp8+EioGfglRPaxvR0N/DNmIEdig2+
2gWJ
dbgFpgXVad1Y42R1hG/lYPrViLRF8yHl4AcPHT3iKDxTONNRQh4COoY/7mUc
BOku
mv7XrDiq+0i6KHewyJdAlJj4xSv3oIgX7VgJSQQxL7F2jio3U0xBCA==
=1efk
-----END PGP SIGNATURE-----
Re: puc based 16550 on macppc?
country flaguser name
United Kingdom		 2007-04-18 04:58:25 
In article
<4affc5e0704171200j3fc5dd8fpbde6a45755a75c84mail.gmail.com> you write:
>Following is the pcictl dump; unfortunately, I do not
understand the
>pci magics all that well... anyone here has experience
with
>puc-attached serial ports?

Well, I've got one in my 9500 running (ahem)2.1:

puc0 at pci0 dev 14 function 0: Lava Computers 2SP-PCI
parallel port (lpt)
lpt0 at puc0 port 0: interrupting at irq 24
puc1 at pci0 dev 14 function 1: Lava Computers dual serial
port (com, com)
com0 at puc1 port 0: interrupting at irq 24
com0: ns16550a, working fifo
com1 at puc1 port 1: interrupting at irq 24
com1: ns16550a, working fifo

As I recall, the serial side of it just worked -- I don't
think I've 
ever tried the parallel side.

-- 
Ben Harris
Re: puc based 16550 on macppc?
user name
 2007-04-18 09:05:18 
On 18/04/07, Michael Lorenz <macallannetbsd.org> wrote:
> Hmm, so OF did try to set up something. The reg
property looks weird
> though.

> Looks like I'll need to look at the puc code - I have
no idea what this
> code does ;)
> One final thing to test though - could you please build
a kernel
> without the puc driver and check if the card's config
space looks any
> different?

Sure:
dmesg:
Lava Semiconductor Manufacturing product 0x0200 (serial
communications, interface 0x03) at pci1 dev 2 function 0
not
configured

ofctl -l:
ff87ab28: /pci80000000/pci-bridged/pci1407,2002

vendor-id               00001407 ........ ........ ........ 
 ....
device-id               00000200 ........ ........ ........ 
 ....
revision-id             00000000 ........ ........ ........ 
 ....
class-code              00070003 ........ ........ ........ 
 ....
interrupts              00000001 ........ ........ ........ 
 ....
min-grant               00000000 ........ ........ ........ 
 ....
max-latency             00000000 ........ ........ ........ 
 ....
subsystem-vendor-id     00001407 ........ ........ ........ 
 ....
subsystem-id            00000200 ........ ........ ........ 
 ....
devsel-speed            00000002 ........ ........ ........ 
 ....
fast-back-to-back
name                    70636931 3430372c 32303000 ........ 
 "pci1407,200"
compatible              70636931 3430372c 32303000 ........ 
 "pci1407,200"
            000c:       70636931 3430372c 32303000 ........ 
 "pci1407,200"
            0018:       70636963 6c617373 2c303730 30303300 
 "pciclass,070003"
reg                     00011000 00000000 00000000 00000000 
 ................
            0010:       00000000 21011010 00000000 00000000 
 ....!...........
            0020:       00000000 00000010 21011014 00000000 
 ........!.......
            0030:       00000000 00000000 00000010 ........ 
 ............
assigned-addresses

I can't see a difference (I guess that means that any
weirdness is due
to OF?).  Do you want pcictl output as well?

BTW, I have one other PCI card in there that OF does not
handle.
Unlike the serial card however, the 3c905b is handled by
NetBSD
without problem and is in fact the primary ethernet card
(since bm0
sucks rocks).

Joe.
Re: puc based 16550 on macppc?
country flaguser name
United States		 2007-04-18 11:45:11 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Apr 18, 2007, at 10:05, Joachim Thiemann wrote:

> On 18/04/07, Michael Lorenz <macallannetbsd.org> wrote:
>> Hmm, so OF did try to set up something. The reg
property looks weird
>> though.
>
>> Looks like I'll need to look at the puc code - I
have no idea what 
>> this
>> code does ;)
>> One final thing to test though - could you please
build a kernel
>> without the puc driver and check if the card's
config space looks any
>> different?
>
> Sure:
> dmesg:
> Lava Semiconductor Manufacturing product 0x0200
(serial
> communications, interface 0x03) at pci1 dev 2 function
0 not
> configured
>
> Do you want pcictl output as well?

Actually that's what I wanted.

> BTW, I have one other PCI card in there that OF does
not handle.
> Unlike the serial card however, the 3c905b is handled
by NetBSD
> without problem and is in fact the primary ethernet
card (since bm0
> sucks rocks).

OF can't use pretty much any card without FCode ROM but in
all cases it 
should properly program their config spaces, as in IRQ line
register, 
BARs etc. - you usually don't need to know what exactly a
PCI device is 
in order to find out what address ranges it needs.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRiZLF8pnzkX8Yg2nAQJXrwf/R1j8BK0yIxAcPbOfRs4bCjxnEnxR
e9SQ
e2wyCpJAZjR4hPkkJ7HY25XqQvStHyTqNylrhmh7NpZExpKV8pYZz2uMNT1F
43od
Knl7nCPgjLUWjFTCHAOgsY/0SZJSspUbOEdI/i0SkPF0UqUTW3D5reR0vJ2h
EuK6
wHpLQviVirLlF42f/huf2LPMi1R3uw6UwvXhfB8Iz3taOXk3YQGDQd76kM16
KLpf
fuzKvEP9rd4NvXCPzRVTSXkdItCVaVNEspTY96o+LPJ9MtbBOLUuwcJY5Iz5
Yb83
yEqzk5f6F9diqs5OiN9qCyCRFxdbFSnKYt04qPEQ49NrOMWjFvSjFg==
=YhZh
-----END PGP SIGNATURE-----
Re: puc based 16550 on macppc?
user name
 2007-04-18 11:56:10 
On 18/04/07, Michael Lorenz <macallannetbsd.org> wrote:
> > Do you want pcictl output as well?
> Actually that's what I wanted.

Oh, ok:
PCI configuration registers:
  Common header:
    0x00: 0x02001407 0x04800040 0x07000300 0x00000000

    Vendor Name: Lava Semiconductor Manufacturing (0x1407)
    Device ID: 0x0200
    Command register: 0x0040
      I/O space accesses: off
      Memory space accesses: off
      Bus mastering: off
      Special cycles: off
      MWI transactions: off
      Palette snooping: off
      Parity error checking: on
      Address/data stepping: off
      System error (SERR): off
      Fast back-to-back transactions: off
    Status register: 0x0480
      Capability List support: off
      66 MHz capable: off
      User Definable Features (UDF) support: off
      Fast back-to-back capable: on
      Data parity error detected: off
      DEVSEL timing: slow (0x2)
      Slave signaled Target Abort: off
      Master received Target Abort: off
      Master received Master Abort: off
      Asserted System Error (SERR): off
      Parity error detected: off
    Class Name: communications (0x07)
    Subclass Name: serial (0x00)
    Interface: 0x03
    Revision ID: 0x00
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x00
    Cache Line Size: 0x00

  Type 0 ("normal" device) header:
    0x10: 0x0000fff9 0x0000fff9 0x00000000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0x02001407
    0x30: 0x00000000 0x00000000 0x00000000 0x00000100

    Base address register at 0x10
      type: i/o
      base: 0x0000fff8, not sized
    Base address register at 0x14
      type: i/o
      base: 0x0000fff8, not sized
    Base address register at 0x18
      not implemented(?)
    Base address register at 0x1c
      not implemented(?)
    Base address register at 0x20
      not implemented(?)
    Base address register at 0x24
      not implemented(?)
    Cardbus CIS Pointer: 0x00000000
    Subsystem vendor ID: 0x1407
    Subsystem ID: 0x0200
    Expansion ROM Base Address: 0x00000000
    Reserved  0x34: 0x00000000
    Reserved  0x38: 0x00000000
    Maximum Latency: 0x00
    Minimum Grant: 0x00
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x00

  Device-dependent header:
    0x40: 0x00000000 0x00000000 0x00000000 0x00000000
    0x50: 0x00000000 0x00000000 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

Joe.
[1-10] [11-17]

about | contact  Other archives ( Real Estate discussion Medical topics )