Minskey, I can not correlate between the scanpci reported resource and
the mdb :
> S2io Inc. Device unknown CardVendor 0x17d5 card 0x6030 (S2io Inc.,
> Card unknown)
> STATUS 0x0010 COMMAND 0x0046
> CLASS 0x02 0x00 0x00 REVISION 0x01
> BIST 0x80 HEADER 0x00 LATENCY 0x00 CACHE 0x10
> BASE2 0xd8002000 SIZE 4096 MEM PREFETCHABLE
> BASE4 0xd8000100 SIZE 256 MEM PREFETCHABLE
> BASEROM 0x00000000 addr 0x00000000
> MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
> *pci_bus_res ::print struct pci_bus_resource mem_space | ::list struct
memlist next | ::print struct memlist
{
address = 0xc0000
size = 0x20000
next = 0xffffff014830f2f0
prev = 0
}
{
address = 0x80200000
size = 0x47e00000
next = 0xffffff014830f190
prev = 0
}
{
address = 0xc8001100
size = 0xf00
next = 0xffffff014830f170
prev = 0
}
{
address = 0xc8003000
size = 0xffd000
next = 0xffffff014830f150
prev = 0
}
{
address = 0xca200000
size = 0x5e00000
next = 0xffffff014830f290
prev = 0
}
{
address = 0xd9000000
size = 0x7000000
next = 0xffffff014850af18
prev = 0
}
{
address = 0xf0000000
size = 0xec00000
next = 0xffffff014850aef8
prev = 0
}
{
address = 0xfec01000
size = 0x1ff000
next = 0xffffff014850aed8
prev = 0
}
{
address = 0xff000000
size = 0x800000
next = 0
prev = 0
}
Thanks,
Eitan
-----Original Message-----
From: driver-discuss-boun...@opensolaris.org
[mailto:driver-discuss-boun...@opensolaris.org] On Behalf Of
driver-discuss-requ...@opensolaris.org
Sent: Wednesday, April 22, 2009 11:19 AM
To: driver-discuss@opensolaris.org
Subject: driver-discuss Digest, Vol 43, Issue 18
Send driver-discuss mailing list submissions to
driver-discuss@opensolaris.org
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
or, via email, send a message with subject or body 'help' to
driver-discuss-requ...@opensolaris.org
You can reach the person managing the list at
driver-discuss-ow...@opensolaris.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of driver-discuss digest..."
Today's Topics:
1. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (minskey guo)
2. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (minskey guo)
3. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (Kerry Shu)
4. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (Eitan Eliahu)
5. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (Eitan Eliahu)
6. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (Kerry Shu)
7. Re: OpenSOlaris build 110 - problem with ddi_regs_map_setup()
on x86 (Eitan Eliahu)
----------------------------------------------------------------------
Message: 1
Date: Wed, 22 Apr 2009 21:40:11 +0800
From: minskey guo <minskey....@gmail.com>
To: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <49ef1e3b.4090...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
You should enjoy powerful mdb & dtrace, which are what I want on Linux
:)
bash# mdb -k
> ::log /var/your-outputs
> *pci_bus_res ::print struct pci_bus_resource mem_space | ::list
struct memlist next | ::print struct memlist
And then, check the file /var/your-outputs
-minskey
Eitan Eliahu ??:
> I would like to print the PCI resources when the driver attach entry
point is being code. Could anyone show me where is this information in
the dev_info structure?
> It seems that the PCI bus drivers does not correctly enumerate the
device object system resources during boot time, when the driver loads
it gets erroneous system resources in the dev_info:
>
>
ttp://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/i
o/pci/pci_boot.c#2159
>
> 2027 base = (uint_t)memlist_find(io_res, len, len);
> 2028 if (base != 0) {
> 2029 memlist_insert(io_res_used, base, len);
> 2030 /* XXX need to worry about 64-bit? */
> 2031 pci_putl(bus, dev, func, offset,
> 2032 base | type);
> 2033 base = pci_getl(bus, dev, func, offset);
> 2034 base &= PCI_BASE_IO_ADDR_M;
> 2035 }
> 2036 if (base == 0) {
> 2037 cmn_err(CE_WARN, "failed to program"
> 2038 " IO space [%d/%d/%d] b...@0x%x"
> 2039 " length 0x%x",
> 2040 bus, dev, func, offset, len);
>
> Thanks,
> Eitan
>
------------------------------
Message: 2
Date: Wed, 22 Apr 2009 22:08:56 +0800
From: minskey guo <minskey....@gmail.com>
To: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <49ef24f8.8020...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
I am not sure, but you can try add "base = NULL"; at
line 2125 see what happens.
-minskey
minskey guo ??:
>
>
> You should enjoy powerful mdb & dtrace, which are what I want on Linux
:)
>
> bash# mdb -k
> > ::log /var/your-outputs
> > *pci_bus_res ::print struct pci_bus_resource mem_space | ::list
> struct memlist next | ::print struct memlist
>
> And then, check the file /var/your-outputs
>
>
> -minskey
>
>
> Eitan Eliahu ??:
>> I would like to print the PCI resources when the driver attach entry
>> point is being code. Could anyone show me where is this information
>> in the dev_info structure?
>> It seems that the PCI bus drivers does not correctly enumerate the
>> device object system resources during boot time, when the driver
>> loads it gets erroneous system resources in the dev_info:
>>
>>
ttp://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/i
o/pci/pci_boot.c#2159
>>
>>
>> 2027 base = (uint_t)memlist_find(io_res, len, len);
>> 2028 if (base != 0) {
>> 2029 memlist_insert(io_res_used, base, len);
>> 2030 /* XXX need to worry about 64-bit? */
>> 2031 pci_putl(bus, dev, func, offset,
>> 2032 base | type);
>> 2033 base = pci_getl(bus, dev, func, offset);
>> 2034 base &= PCI_BASE_IO_ADDR_M;
>> 2035 }
>> 2036 if (base == 0) {
>> 2037 cmn_err(CE_WARN, "failed to program"
>> 2038 " IO space [%d/%d/%d] b...@0x%x"
>> 2039 " length 0x%x",
>> 2040 bus, dev, func, offset, len);
>>
>> Thanks,
>> Eitan
>>
>
>
------------------------------
Message: 3
Date: Wed, 22 Apr 2009 10:22:39 -0700
From: Kerry Shu <kerry....@sun.com>
To: Eitan Eliahu <eitan.eli...@neterion.com>,
gireesh.nagabhush...@neterion.com
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <49ef525f.9070...@sun.com>
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Could you post the '/usr/X11/bin/scanpci -v' result? And what is your
device ID?
I saw you mentioned:
WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100
While Gireesh mentioned:
WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
Are you two talking about same issue or not?
Regards,
Kerry
Eitan Eliahu wrote:
> We found that whenever the following message is displayed the driver
fails to read the mapped memory for the first BAR.
> "WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100"
>
>
> This warning message is output here:
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/
io/pci/pci_boot.c#2159
>
> 2027 base = (uint_t)memlist_find(io_res, len, len);
> 2028 if (base != 0) {
> 2029 memlist_insert(io_res_used, base, len);
> 2030 /* XXX need to worry about 64-bit? */
> 2031 pci_putl(bus, dev, func, offset,
> 2032 base | type);
> 2033 base = pci_getl(bus, dev, func, offset);
> 2034 base &= PCI_BASE_IO_ADDR_M;
> 2035 }
> 2036 if (base == 0) {
> 2037 cmn_err(CE_WARN, "failed to program"
> 2038 " IO space [%d/%d/%d] b...@0x%x"
> 2039 " length 0x%x",
> 2040 bus, dev, func, offset, len);
>
> Thanks,
> Eitan
------------------------------
Message: 4
Date: Wed, 22 Apr 2009 13:26:11 -0400
From: "Eitan Eliahu" <eitan.eli...@neterion.com>
To: <kerry....@sun.com>, "Gireesh Nagabhushana"
<gireesh.nagabhush...@neterion.com>
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <78c9135a3d2ece4b8162ebdce82cad7705313...@nekter>
Content-Type: text/plain; charset="us-ascii"
Hi Kerry,
Yes, Girresh and I dealing with the same issue.
Here is the output for the scanpci command on this device:
pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x17d5 device 0x5833
S2io Inc. Device unknown
CardVendor 0x17d5 card 0x6030 (S2io Inc., Card unknown)
STATUS 0x0010 COMMAND 0x0046
CLASS 0x02 0x00 0x00 REVISION 0x01
BIST 0x80 HEADER 0x00 LATENCY 0x00 CACHE 0x10
BASE2 0xd8002000 SIZE 4096 MEM PREFETCHABLE
BASE4 0xd8000100 SIZE 256 MEM PREFETCHABLE
BASEROM 0x00000000 addr 0x00000000
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
Thank you,
Eitan
-----Original Message-----
From: kerry....@sun.com [mailto:kerry....@sun.com]
Sent: Wednesday, April 22, 2009 10:23 AM
To: Eitan Eliahu; Gireesh Nagabhushana
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Could you post the '/usr/X11/bin/scanpci -v' result? And what is your
device ID?
I saw you mentioned:
WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100
While Gireesh mentioned:
WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
Are you two talking about same issue or not?
Regards,
Kerry
Eitan Eliahu wrote:
> We found that whenever the following message is displayed the driver
fails to read the mapped memory for the first BAR.
> "WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100"
>
>
> This warning message is output here:
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/
io/pci/pci_boot.c#2159
>
> 2027 base = (uint_t)memlist_find(io_res, len, len);
> 2028 if (base != 0) {
> 2029 memlist_insert(io_res_used, base, len);
> 2030 /* XXX need to worry about 64-bit? */
> 2031 pci_putl(bus, dev, func, offset,
> 2032 base | type);
> 2033 base = pci_getl(bus, dev, func, offset);
> 2034 base &= PCI_BASE_IO_ADDR_M;
> 2035 }
> 2036 if (base == 0) {
> 2037 cmn_err(CE_WARN, "failed to program"
> 2038 " IO space [%d/%d/%d] b...@0x%x"
> 2039 " length 0x%x",
> 2040 bus, dev, func, offset, len);
>
> Thanks,
> Eitan
------------------------------
Message: 5
Date: Wed, 22 Apr 2009 13:30:21 -0400
From: "Eitan Eliahu" <eitan.eli...@neterion.com>
To: "Eitan Eliahu" <eitan.eli...@neterion.com>, <kerry....@sun.com>,
"Gireesh Nagabhushana" <gireesh.nagabhush...@neterion.com>
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <78c9135a3d2ece4b8162ebdce82cad7705313...@nekter>
Content-Type: text/plain; charset="us-ascii"
Please consider only this warning message:
WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
For the device 0x5833, bus=0, dev=0 and func=0.
Thanks,
Eitan
-----Original Message-----
From: Eitan Eliahu
Sent: Wednesday, April 22, 2009 10:26 AM
To: 'kerry....@sun.com'; Gireesh Nagabhushana
Cc: driver-discuss@opensolaris.org
Subject: RE: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Hi Kerry,
Yes, Girresh and I dealing with the same issue.
Here is the output for the scanpci command on this device:
pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x17d5 device 0x5833
S2io Inc. Device unknown
CardVendor 0x17d5 card 0x6030 (S2io Inc., Card unknown)
STATUS 0x0010 COMMAND 0x0046
CLASS 0x02 0x00 0x00 REVISION 0x01
BIST 0x80 HEADER 0x00 LATENCY 0x00 CACHE 0x10
BASE2 0xd8002000 SIZE 4096 MEM PREFETCHABLE
BASE4 0xd8000100 SIZE 256 MEM PREFETCHABLE
BASEROM 0x00000000 addr 0x00000000
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
Thank you,
Eitan
-----Original Message-----
From: kerry....@sun.com [mailto:kerry....@sun.com]
Sent: Wednesday, April 22, 2009 10:23 AM
To: Eitan Eliahu; Gireesh Nagabhushana
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Could you post the '/usr/X11/bin/scanpci -v' result? And what is your
device ID?
I saw you mentioned:
WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100
While Gireesh mentioned:
WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
Are you two talking about same issue or not?
Regards,
Kerry
Eitan Eliahu wrote:
> We found that whenever the following message is displayed the driver
fails to read the mapped memory for the first BAR.
> "WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100"
>
>
> This warning message is output here:
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/
io/pci/pci_boot.c#2159
>
> 2027 base = (uint_t)memlist_find(io_res, len, len);
> 2028 if (base != 0) {
> 2029 memlist_insert(io_res_used, base, len);
> 2030 /* XXX need to worry about 64-bit? */
> 2031 pci_putl(bus, dev, func, offset,
> 2032 base | type);
> 2033 base = pci_getl(bus, dev, func, offset);
> 2034 base &= PCI_BASE_IO_ADDR_M;
> 2035 }
> 2036 if (base == 0) {
> 2037 cmn_err(CE_WARN, "failed to program"
> 2038 " IO space [%d/%d/%d] b...@0x%x"
> 2039 " length 0x%x",
> 2040 bus, dev, func, offset, len);
>
> Thanks,
> Eitan
------------------------------
Message: 6
Date: Wed, 22 Apr 2009 10:42:14 -0700
From: Kerry Shu <kerry....@sun.com>
To: Eitan Eliahu <eitan.eli...@neterion.com>
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <49ef56f6.4090...@sun.com>
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
I also need the info of other devices, pls sent me the *whole*
result of the "scanpci -v" result. Since [4/0/0] are requesting
8M size MEM space, I want to make sure if such size is available at
its parent bridge or not.
BTW, I saw the device's BASE2/BASE4 are assigned with valid value.
What's the difference between BASE0 and BASE2/BASE4 in the device h/w
spec.
Regards,
Kerry
Eitan Eliahu wrote:
> Please consider only this warning message:
> WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
> For the device 0x5833, bus=0, dev=0 and func=0.
> Thanks,
> Eitan
>
> -----Original Message-----
> From: Eitan Eliahu
> Sent: Wednesday, April 22, 2009 10:26 AM
> To: 'kerry....@sun.com'; Gireesh Nagabhushana
> Cc: driver-discuss@opensolaris.org
> Subject: RE: [driver-discuss] OpenSOlaris build 110 - problem with
> ddi_regs_map_setup() on x86
>
>
> Hi Kerry,
> Yes, Girresh and I dealing with the same issue.
> Here is the output for the scanpci command on this device:
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x17d5 device 0x5833
> S2io Inc. Device unknown
> CardVendor 0x17d5 card 0x6030 (S2io Inc., Card unknown)
> STATUS 0x0010 COMMAND 0x0046
> CLASS 0x02 0x00 0x00 REVISION 0x01
> BIST 0x80 HEADER 0x00 LATENCY 0x00 CACHE 0x10
> BASE2 0xd8002000 SIZE 4096 MEM PREFETCHABLE
> BASE4 0xd8000100 SIZE 256 MEM PREFETCHABLE
> BASEROM 0x00000000 addr 0x00000000
> MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
> Thank you,
> Eitan
>
> -----Original Message-----
> From: kerry....@sun.com [mailto:kerry....@sun.com]
> Sent: Wednesday, April 22, 2009 10:23 AM
> To: Eitan Eliahu; Gireesh Nagabhushana
> Cc: driver-discuss@opensolaris.org
> Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
> ddi_regs_map_setup() on x86
>
> Could you post the '/usr/X11/bin/scanpci -v' result? And what is your
> device ID?
>
> I saw you mentioned:
> WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100
> While Gireesh mentioned:
> WARNING: failed to program mem space [4/0/0] b...@0x10 length
0x800000
>
> Are you two talking about same issue or not?
>
> Regards,
> Kerry
>
>
> Eitan Eliahu wrote:
>> We found that whenever the following message is displayed the driver
> fails to read the mapped memory for the first BAR.
>> "WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100"
>>
>>
>> This warning message is output here:
>>
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/
> io/pci/pci_boot.c#2159
>> 2027 base = (uint_t)memlist_find(io_res, len, len);
>> 2028 if (base != 0) {
>> 2029 memlist_insert(io_res_used, base, len);
>> 2030 /* XXX need to worry about 64-bit? */
>> 2031 pci_putl(bus, dev, func, offset,
>> 2032 base | type);
>> 2033 base = pci_getl(bus, dev, func, offset);
>> 2034 base &= PCI_BASE_IO_ADDR_M;
>> 2035 }
>> 2036 if (base == 0) {
>> 2037 cmn_err(CE_WARN, "failed to program"
>> 2038 " IO space [%d/%d/%d] b...@0x%x"
>> 2039 " length 0x%x",
>> 2040 bus, dev, func, offset, len);
>>
>> Thanks,
>> Eitan
------------------------------
Message: 7
Date: Wed, 22 Apr 2009 14:18:34 -0400
From: "Eitan Eliahu" <eitan.eli...@neterion.com>
To: <kerry....@sun.com>
Cc: driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
Message-ID: <78c9135a3d2ece4b8162ebdce82cad7705313...@nekter>
Content-Type: text/plain; charset="us-ascii"
I don't know why the scanpci names these bars as BAR2 and 4.
Attached is the full output of the scanpci command. It looks like one of
the BARs is missing (BAR0 with size of 0x7fffff). BASE4 is the MSI-X
vector.
Here the configuration space for this device on the Windows OS:
Common Header:
00: VendorID 17d5
02: DeviceID 5833
04: Command 0546 MemSpaceEn BusInitiate PERREn SERREn
InterruptDis
06: Status 0010 CapList
08: RevisionID 01
09: ProgIF 00
0a: SubClass 00 Ethernet Controller
0b: BaseClass 02 Network Controller
0c: CacheLineSize 0010 BurstDisabled
0d: LatencyTimer 00
0e: HeaderType 00
0f: BIST 80
10: BAR0 d880000c
14: BAR1 00000000
18: BAR2 d87ff00c
1c: BAR3 00000000
20: BAR4 d87fec0c
24: BAR5 00000000
28: CBCISPtr 00000000
2c: SubSysVenID 17d5
2e: SubSysID 6031
30: ROMBAR 00000000
34: CapPtr 40
3c: IntLine 00
3d: IntPin 01
3e: MinGnt 00
3f: MaxLat 00
Device Private:
40: 7e237001 00000000 00000000 00000000
50: 01860005 00000000 00000000 00000000
60: 00000000 0000000f 00000000 00000000
70: 1001a010 10008345 00002034 00112c81
80: 30810000 00000000 00000000 00000000
90: 00000000 0000001f 00000000 00000000
a0: 8043c011 00000002 00000802 00000000
b0: 00000000 00000000 00000000 00000000
c0: 807c5003 00000000 00000000 00000000
d0: 00000000 00000000 00000000 00000000
e0: 00000000 00000000 00000000 00000000
f0: 00000000 00000000 00000000 00000000
Thanks,
Eitan
-----Original Message-----
From: kerry....@sun.com [mailto:kerry....@sun.com]
Sent: Wednesday, April 22, 2009 10:42 AM
To: Eitan Eliahu
Cc: Gireesh Nagabhushana; driver-discuss@opensolaris.org
Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
ddi_regs_map_setup() on x86
I also need the info of other devices, pls sent me the *whole*
result of the "scanpci -v" result. Since [4/0/0] are requesting
8M size MEM space, I want to make sure if such size is available at
its parent bridge or not.
BTW, I saw the device's BASE2/BASE4 are assigned with valid value.
What's the difference between BASE0 and BASE2/BASE4 in the device h/w
spec.
Regards,
Kerry
Eitan Eliahu wrote:
> Please consider only this warning message:
> WARNING: failed to program mem space [4/0/0] b...@0x10 length 0x800000
> For the device 0x5833, bus=0, dev=0 and func=0.
> Thanks,
> Eitan
>
> -----Original Message-----
> From: Eitan Eliahu
> Sent: Wednesday, April 22, 2009 10:26 AM
> To: 'kerry....@sun.com'; Gireesh Nagabhushana
> Cc: driver-discuss@opensolaris.org
> Subject: RE: [driver-discuss] OpenSOlaris build 110 - problem with
> ddi_regs_map_setup() on x86
>
>
> Hi Kerry,
> Yes, Girresh and I dealing with the same issue.
> Here is the output for the scanpci command on this device:
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x17d5 device 0x5833
> S2io Inc. Device unknown
> CardVendor 0x17d5 card 0x6030 (S2io Inc., Card unknown)
> STATUS 0x0010 COMMAND 0x0046
> CLASS 0x02 0x00 0x00 REVISION 0x01
> BIST 0x80 HEADER 0x00 LATENCY 0x00 CACHE 0x10
> BASE2 0xd8002000 SIZE 4096 MEM PREFETCHABLE
> BASE4 0xd8000100 SIZE 256 MEM PREFETCHABLE
> BASEROM 0x00000000 addr 0x00000000
> MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
> Thank you,
> Eitan
>
> -----Original Message-----
> From: kerry....@sun.com [mailto:kerry....@sun.com]
> Sent: Wednesday, April 22, 2009 10:23 AM
> To: Eitan Eliahu; Gireesh Nagabhushana
> Cc: driver-discuss@opensolaris.org
> Subject: Re: [driver-discuss] OpenSOlaris build 110 - problem with
> ddi_regs_map_setup() on x86
>
> Could you post the '/usr/X11/bin/scanpci -v' result? And what is your
> device ID?
>
> I saw you mentioned:
> WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100
> While Gireesh mentioned:
> WARNING: failed to program mem space [4/0/0] b...@0x10 length
0x800000
>
> Are you two talking about same issue or not?
>
> Regards,
> Kerry
>
>
> Eitan Eliahu wrote:
>> We found that whenever the following message is displayed the driver
> fails to read the mapped memory for the first BAR.
>> "WARNING: failed to program mem space [0/31/3] b...@0x10 length 0x100"
>>
>>
>> This warning message is output here:
>>
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/
> io/pci/pci_boot.c#2159
>> 2027 base = (uint_t)memlist_find(io_res, len, len);
>> 2028 if (base != 0) {
>> 2029 memlist_insert(io_res_used, base, len);
>> 2030 /* XXX need to worry about 64-bit? */
>> 2031 pci_putl(bus, dev, func, offset,
>> 2032 base | type);
>> 2033 base = pci_getl(bus, dev, func, offset);
>> 2034 base &= PCI_BASE_IO_ADDR_M;
>> 2035 }
>> 2036 if (base == 0) {
>> 2037 cmn_err(CE_WARN, "failed to program"
>> 2038 " IO space [%d/%d/%d] b...@0x%x"
>> 2039 " length 0x%x",
>> 2040 bus, dev, func, offset, len);
>>
>> Thanks,
>> Eitan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pci-device
Type: application/octet-stream
Size: 11275 bytes
Desc: pci-device
URL:
<http://mail.opensolaris.org/pipermail/driver-discuss/attachments/200904
22/6b5155bc/attachment.obj>
------------------------------
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
End of driver-discuss Digest, Vol 43, Issue 18
**********************************************
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
