about SdBusOpenInterface() and SDIO

the sdbusapi.doc said, the SdBusOpenInterface() should be called in
AddDevice(), but I develop a driver for NDIS NIC, then I have no this
callback routine , I call it in my MiniportInitialize(),but it failed all
the time,I have no idea.
please help me, if you know this.

and it said, SD function drivers are WDM drivers that are linked to the SD
bus driver lib.they are not minport driver like NDIS or SCSI driver.
How to understand it?who can explain for me. thanks!

THX very much!

AMon

pavel_a
Tue May 24 08:47:15 CDT 2005

Your driver is installed for the SD device ID, it isn't root enumerated?
NdisMGetDeviceProperty returns valid pointer in Adapter->PhyDeviceObject ?

--PA

"iwub" wrote:
> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
> callback routine , I call it in my MiniportInitialize(),but it failed all
> the time,I have no idea.
> please help me, if you know this.
>
> and it said, SD function drivers are WDM drivers that are linked to the SD
> bus driver lib.they are not minport driver like NDIS or SCSI driver.
> How to understand it?who can explain for me. thanks!
>
> THX very much!
>
> AMon
>
>
>

iwub
Tue May 24 20:10:22 CDT 2005

the driver is intalled by hand, it is not detected by host.(is it the device
problem?)
My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function driver).
what will hanppen then? the device must be find by system itself?

thanks

"Pavel A." <pavel_a@NOwritemeNO.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
> Your driver is installed for the SD device ID, it isn't root enumerated?
> NdisMGetDeviceProperty returns valid pointer in Adapter->PhyDeviceObject ?
>
> --PA
>
> "iwub" wrote:
>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>> callback routine , I call it in my MiniportInitialize(),but it failed all
>> the time,I have no idea.
>> please help me, if you know this.
>>
>> and it said, SD function drivers are WDM drivers that are linked to the
>> SD
>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>> How to understand it?who can explain for me. thanks!
>>
>> THX very much!
>>
>> AMon
>>
>>
>>

Doron
Wed May 25 02:53:10 CDT 2005

yes. you must let the system find the device and your INF must match the
SDBUS hardware ID generated for your device.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"iwub" <iwub@etang.com> wrote in message
news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
> the driver is intalled by hand, it is not detected by host.(is it the
> device problem?)
> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
> driver).
> what will hanppen then? the device must be find by system itself?
>
> thanks
>
> "Pavel A." <pavel_a@NOwritemeNO.com>
> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>> Your driver is installed for the SD device ID, it isn't root enumerated?
>> NdisMGetDeviceProperty returns valid pointer in Adapter->PhyDeviceObject
>> ?
>>
>> --PA
>>
>> "iwub" wrote:
>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>> all
>>> the time,I have no idea.
>>> please help me, if you know this.
>>>
>>> and it said, SD function drivers are WDM drivers that are linked to the
>>> SD
>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>> How to understand it?who can explain for me. thanks!
>>>
>>> THX very much!
>>>
>>> AMon
>>>
>>>
>>>
>
>

iwub
Wed May 25 04:13:56 CDT 2005

Hi,
and I strange phenomenon ,
when I use device manager to renew my adapter's driver(it now exists in my
NIC tree), the device manager find another device that name "XXX 802.11
SDIO", but my name for the device is "XXX 6100 802.11 Adapter", why ?

thanks,

"Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
> yes. you must let the system find the device and your INF must match the
> SDBUS hardware ID generated for your device.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "iwub" <iwub@etang.com> wrote in message
> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>> the driver is intalled by hand, it is not detected by host.(is it the
>> device problem?)
>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>> driver).
>> what will hanppen then? the device must be find by system itself?
>>
>> thanks
>>
>> "Pavel A." <pavel_a@NOwritemeNO.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>> Your driver is installed for the SD device ID, it isn't root enumerated?
>>> NdisMGetDeviceProperty returns valid pointer in Adapter->PhyDeviceObject
>>> ?
>>>
>>> --PA
>>>
>>> "iwub" wrote:
>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>> all
>>>> the time,I have no idea.
>>>> please help me, if you know this.
>>>>
>>>> and it said, SD function drivers are WDM drivers that are linked to the
>>>> SD
>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>> How to understand it?who can explain for me. thanks!
>>>>
>>>> THX very much!
>>>>
>>>> AMon
>>>>
>>>>
>>>>
>>
>>
>
>

Doron
Wed May 25 10:12:47 CDT 2005

device manager will show the name that the INF specified if there is a
driver installed, otherwise it will show the name of the device as reported
by the device itself. perhaps your device's firmware reports "XXX 802.11
SDIO"

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"iwub" <iwub@etang.com> wrote in message
news:%232alDpQYFHA.3164@TK2MSFTNGP09.phx.gbl...
> Hi,
> and I strange phenomenon ,
> when I use device manager to renew my adapter's driver(it now exists in my
> NIC tree), the device manager find another device that name "XXX 802.11
> SDIO", but my name for the device is "XXX 6100 802.11 Adapter", why ?
>
> thanks,
>
> "Doron Holan [MS]" <doronh@nospam.microsoft.com>
> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
>> yes. you must let the system find the device and your INF must match the
>> SDBUS hardware ID generated for your device.
>>
>> d
>>
>> --
>> Please do not send e-mail directly to this alias. this alias is for
>> newsgroup purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "iwub" <iwub@etang.com> wrote in message
>> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>>> the driver is intalled by hand, it is not detected by host.(is it the
>>> device problem?)
>>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>>> driver).
>>> what will hanppen then? the device must be find by system itself?
>>>
>>> thanks
>>>
>>> "Pavel A." <pavel_a@NOwritemeNO.com>
>>> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>>> Your driver is installed for the SD device ID, it isn't root
>>>> enumerated?
>>>> NdisMGetDeviceProperty returns valid pointer in
>>>> Adapter->PhyDeviceObject ?
>>>>
>>>> --PA
>>>>
>>>> "iwub" wrote:
>>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>>> all
>>>>> the time,I have no idea.
>>>>> please help me, if you know this.
>>>>>
>>>>> and it said, SD function drivers are WDM drivers that are linked to
>>>>> the SD
>>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>>> How to understand it?who can explain for me. thanks!
>>>>>
>>>>> THX very much!
>>>>>
>>>>> AMon
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>

Maxim
Wed May 25 14:04:03 CDT 2005

> device manager will show the name that the INF specified if there is a
> driver installed, otherwise it will show the name of the device as reported
> by the device itself. perhaps your device's firmware reports "XXX 802.11
> SDIO"

More so. In the "otherwise" case, Device Manager will show the result of
MN_QUERY_DEVICE_TEXT IRP from the bus driver. The functional driver for such a
device is not existing (not installed).

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

iwub
Thu May 26 02:11:11 CDT 2005

I have opened the device once, but after that, the machine was reboot and
can not open too, like before.
will it be hardware error?
and our firmware is downloaded before we set any registers or doing 802.11
functions.
what may it happen?

Amon
"Maxim S. Shatskih" <maxim@storagecraft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:eCjb5xVYFHA.3040@TK2MSFTNGP14.phx.gbl...
>> device manager will show the name that the INF specified if there is a
>> driver installed, otherwise it will show the name of the device as
>> reported
>> by the device itself. perhaps your device's firmware reports "XXX 802.11
>> SDIO"
>
> More so. In the "otherwise" case, Device Manager will show the result of
> MN_QUERY_DEVICE_TEXT IRP from the bus driver. The functional driver for
> such a
> device is not existing (not installed).
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
>

iwub
Thu May 26 02:59:27 CDT 2005

This is reported by dbgview tool. I think it should be HW error.

Why?

00000281 44.00235281 SetClockRate: Requested: 100000, Setting to:
187500 Hz in 1-bit

00000282 44.00478441 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000283 44.00549288 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000284 44.00620191 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000285 44.11046991 CIS DUMP: CIS address=0x8000>>>>>>>>>>>>>

00000286 44.11047605 15

00000287 44.11047996 40

00000288 44.11048387 01

00000289 44.11048751 00

00000290 44.11049142 4D

00000291 44.11049533 61

00000292 44.11049896 72

00000293 44.11050259 76

00000294 44.11050650 65

00000295 44.11051041 6C

00000296 44.11051405 6C

00000297 44.11051796 20

00000298 44.11052187 53

00000299 44.11052578 65

00000300 44.11052941 6D

00000301 44.11053304 69

00000302 44.11053639

00000303 44.11054031 63

00000304 44.11054422 6F

00000305 44.11054785 6E

00000306 44.11055148 64

00000307 44.11055539 75

00000308 44.11055930 63

00000309 44.11056321 74

00000310 44.11056685 6F

00000311 44.11057076 72

00000312 44.11057439 00

00000313 44.11057830 49

00000314 44.11058221 42

00000315 44.11058612 49

00000316 44.11058975 53

00000317 44.11059339 20

00000318 44.11059730 57

00000319 44.11060065

00000320 44.11060428 69

00000321 44.11060791 72

00000322 44.11061154 65

00000323 44.11061546 6C

00000324 44.11061937 65

00000325 44.11062328 73

00000326 44.11062719 73

00000327 44.11063110 20

00000328 44.11063501 53

00000329 44.11063892 44

00000330 44.11064283 49

00000331 44.11064674 4F

00000332 44.11065038 20

00000333 44.11065401 43

00000334 44.11065764 61

00000335 44.11066155 72

00000336 44.11066490

00000337 44.11066853 64

00000338 44.11067217 00

00000339 44.11067580 56

00000340 44.11067943 65

00000341 44.11068306 72

00000342 44.11068669 73

00000343 44.11069060 69

00000344 44.11069452 6F

00000345 44.11069815 6E

00000346 44.11070206 20

00000347 44.11070597 31

00000348 44.11070988 2E

00000349 44.11071351 30

00000350 44.11071714 00

00000351 44.11072078 00

00000352 44.11072441 00

00000353 44.11072748

00000354 44.11073111 00

00000355 44.11073502 FF

00000356 44.11073893 20

00000357 44.11074257 04

00000358 44.11074648 DF

00000359 44.11075011 02

00000360 44.11075374 03

00000361 44.11075765 91

00000362 44.11076156 21

00000363 44.11076520 02

00000364 44.11076883 0C

00000365 44.11077246 00

00000366 44.11077609 22

00000367 44.11077972 04

00000368 44.11078335 00

00000369 44.11078699 00

00000370 44.11079006

00000371 44.11079369 01

00000372 44.11079760 32

00000373 44.11080151 FF

00000374 44.11080514 00

00000375 44.11080906 7F

00000376 44.11081297 E0

00000377 44.11081660 80

00000378 44.11082023 91

00000379 44.11082414 CA

00000380 44.11082777 1F

00000381 44.11083140 E9

00000382 44.11083532 23

00000383 44.11083923 E0

00000384 44.11084286 50

00000385 44.11084649 A2

00000386 44.11085040 3F

00000387 44.11085347

00000388 44.11085711 75

00000389 44.11086074 F3

00000390 44.11086437 E3

00000391 44.11086828 12

00000392 44.11087219 BB

00000393 44.11087582 D5

00000394 44.11087946 40

00000395 44.11088337 5B

00000396 44.11088700 DC

00000397 44.11089063 FB

00000398 44.11089454 45

00000399 44.11089845 E9

00000400 44.11090208 72

00000401 44.11090600 D8

00000402 44.11090991 F7

00000403 44.11091382 51

00000404 44.11091717

00000405 44.11092080 D5

00000406 44.11092443 50

00000407 44.11092834 2D

00000408 44.11093226 93

00000409 44.11093589 73

00000410 44.11093952 F9

00000411 44.11094343 EC

00000412 44.11094734 02

00000413 44.11095125 F3

00000414 44.11095488 C0

00000415 44.11095852 84

00000416 44.11096215 CF

00000417 44.11096606 0D

00000418 44.11096997 E6

00000419 44.11097360 F7

00000420 44.11097751 CF

00000421 44.11098086

00000422 44.11098450 CIS DUMP<<<<<<<<<<<<<<

00000423 52.76607278 >RemoveCard

00000424 53.27809289 <RemoveCard

00000425 69.00149572 SetClockRate: Requested: 100000, Setting to:
187500 Hz in 1-bit

00000426 69.00389016 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000427 69.00474697 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000428 69.00559429 CMD 52 Status error 24, response = ffffffff
arg = 88000c08

00000429 69.11011930 CIS DUMP: CIS address=0x8000>>>>>>>>>>>>>

00000430 69.11012461 15

00000431 69.11012824 40

00000432 69.11013187 01

00000433 69.11013551 00

00000434 69.11013942 4D

00000435 69.11014305 61

00000436 69.11014696 72

00000437 69.11015087 76

00000438 69.11015478 65

00000439 69.11015869 6C

00000440 69.11016233 6C

00000441 69.11016596 20

00000442 69.11016987 53

00000443 69.11017378 65

00000444 69.11017741 6D

00000445 69.11018104 69

00000446 69.11018439

00000447 69.11018803 63

00000448 69.11019194 6F

00000449 69.11019557 6E

00000450 69.11019920 64

00000451 69.11020311 75

00000452 69.11020702 63

00000453 69.11021066 74

00000454 69.11021429 6F

00000455 69.11021792 72

00000456 69.11022155 00

00000457 69.11022546 49

00000458 69.11022937 42

00000459 69.11023328 49

00000460 69.11023692 53

00000461 69.11024055 20

00000462 69.11024418 57

00000463 69.11024753

00000464 69.11025144 69

00000465 69.11025507 72

00000466 69.11025871 65

00000467 69.11026262 6C

00000468 69.11026653 65

00000469 69.11027016 73

00000470 69.11027379 73

00000471 69.11027742 20

00000472 69.11028106 53

00000473 69.11028469 44

00000474 69.11028860 49

00000475 69.11029251 4F

00000476 69.11029614 20

00000477 69.11029977 43

00000478 69.11030340 61

00000479 69.11030704 72

00000480 69.11031011

00000481 69.11031374 64

00000482 69.11031737 00

00000483 69.11032128 56

00000484 69.11032519 65

00000485 69.11032911 72

00000486 69.11033302 73

00000487 69.11033693 69

00000488 69.11034056 6F

00000489 69.11034447 6E

00000490 69.11034838 20

00000491 69.11035229 31

00000492 69.11035620 2E

00000493 69.11035984 30

00000494 69.11036347 00

00000495 69.11036710 00

00000496 69.11037073 00

00000497 69.11037380

00000498 69.11037744 00

00000499 69.11038135 FF

00000500 69.11038526 20

00000501 69.11038889 04

00000502 69.11039280 DF

00000503 69.11039643 02

00000504 69.11040006 03

00000505 69.11040370 91

00000506 69.11040761 21

00000507 69.11041124 02

00000508 69.11041487 0C

00000509 69.11041850 00

00000510 69.11042213 22

00000511 69.11042577 04

00000512 69.11042940 00

00000513 69.11043303 00

00000514 69.11043610

00000515 69.11043973 01

00000516 69.11044365 32

00000517 69.11044728 FF

00000518 69.11045119 00

00000519 69.11045510 7F

00000520 69.11045873 A8

00000521 69.11046264 88

00000522 69.11046655 91

00000523 69.11047885 EA

00000524 69.11048248 1F

00000525 69.11048611 C9

00000526 69.11048974 22

00000527 69.11049365 E0

00000528 69.11049728 52

00000529 69.11050092 C0

00000530 69.11050483 2F

00000531 69.11050818

00000532 69.11051209 55

00000533 69.11051600 F3

00000534 69.11051963 F3

00000535 69.11052326 32

00000536 69.11052718 9B

00000537 69.11053109 DD

00000538 69.11053472 40

00000539 69.11053835 52

00000540 69.11054226 DC

00000541 69.11054589 FB

00000542 69.11054980 65

00000543 69.11055372 E1

00000544 69.11055735 E2

00000545 69.11056098 F0

00000546 69.11056489 B7

00000547 69.11056880 51

00000548 69.11057187

00000549 69.11057579 F4

00000550 69.11057970 50

00000551 69.11058361 2D

00000552 69.11058724 13

00000553 69.11059087 72

00000554 69.11059450 B9

00000555 69.11059841 EC

00000556 69.11060205 02

00000557 69.11060568 F1

00000558 69.11060931 C0

00000559 69.11061322 84

00000560 69.11061713 8E

00000561 69.11062076 4D

00000562 69.11062439 E6

00000563 69.11062803 D7

00000564 69.11063194 CF

00000565 69.11063501

00000566 69.11063892 CIS DUMP<<<<<<<<<<<<<<

00000567 73.98269836 >RemoveCard

00000568 74.49475171 <RemoveCard

"Maxim S. Shatskih" <maxim@storagecraft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:eCjb5xVYFHA.3040@TK2MSFTNGP14.phx.gbl...
>> device manager will show the name that the INF specified if there is a
>> driver installed, otherwise it will show the name of the device as
>> reported
>> by the device itself. perhaps your device's firmware reports "XXX 802.11
>> SDIO"
>
> More so. In the "otherwise" case, Device Manager will show the result of
> MN_QUERY_DEVICE_TEXT IRP from the bus driver. The functional driver for
> such a
> device is not existing (not installed).
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
>

iwub
Thu May 26 05:38:37 CDT 2005

Then how to let the system know I insert the device?
the system did not find the device insert when I insert the SDIO card.

the HW ID is correct. I think.

"Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
> yes. you must let the system find the device and your INF must match the
> SDBUS hardware ID generated for your device.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "iwub" <iwub@etang.com> wrote in message
> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>> the driver is intalled by hand, it is not detected by host.(is it the
>> device problem?)
>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>> driver).
>> what will hanppen then? the device must be find by system itself?
>>
>> thanks
>>
>> "Pavel A." <pavel_a@NOwritemeNO.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>> Your driver is installed for the SD device ID, it isn't root enumerated?
>>> NdisMGetDeviceProperty returns valid pointer in Adapter->PhyDeviceObject
>>> ?
>>>
>>> --PA
>>>
>>> "iwub" wrote:
>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>> all
>>>> the time,I have no idea.
>>>> please help me, if you know this.
>>>>
>>>> and it said, SD function drivers are WDM drivers that are linked to the
>>>> SD
>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>> How to understand it?who can explain for me. thanks!
>>>>
>>>> THX very much!
>>>>
>>>> AMon
>>>>
>>>>
>>>>
>>
>>
>
>

Doron
Fri May 27 00:34:44 CDT 2005

there is probably something wrong about your card. The SD bus is a pnp bus,
it will auto detect your card upon insertion.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"iwub" <iwub@etang.com> wrote in message
news:OTBkC9dYFHA.2128@TK2MSFTNGP14.phx.gbl...
> Then how to let the system know I insert the device?
> the system did not find the device insert when I insert the SDIO card.
>
>
> the HW ID is correct. I think.
>
>
> "Doron Holan [MS]" <doronh@nospam.microsoft.com>
> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
>> yes. you must let the system find the device and your INF must match the
>> SDBUS hardware ID generated for your device.
>>
>> d
>>
>> --
>> Please do not send e-mail directly to this alias. this alias is for
>> newsgroup purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "iwub" <iwub@etang.com> wrote in message
>> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>>> the driver is intalled by hand, it is not detected by host.(is it the
>>> device problem?)
>>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>>> driver).
>>> what will hanppen then? the device must be find by system itself?
>>>
>>> thanks
>>>
>>> "Pavel A." <pavel_a@NOwritemeNO.com>
>>> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>>> Your driver is installed for the SD device ID, it isn't root
>>>> enumerated?
>>>> NdisMGetDeviceProperty returns valid pointer in
>>>> Adapter->PhyDeviceObject ?
>>>>
>>>> --PA
>>>>
>>>> "iwub" wrote:
>>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>>> all
>>>>> the time,I have no idea.
>>>>> please help me, if you know this.
>>>>>
>>>>> and it said, SD function drivers are WDM drivers that are linked to
>>>>> the SD
>>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>>> How to understand it?who can explain for me. thanks!
>>>>>
>>>>> THX very much!
>>>>>
>>>>> AMon
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>

iwub
Fri May 27 01:26:15 CDT 2005

Yes, I think that there is wrong.It should be detected by system when
inserting.
I now open the SD bus interface by scanning by hand, then system find the
new device, I use the setup guide to setup.
but when I got the SdBusIfStd structure, the
Adapter->SdBusIfStd.InitializeInterface() failed.
I called such as the sdbusapi.doc said.please check the below.

THX.

pDevice = Adapter->PhyDeviceObject;
KdPrint( ("SdBusOpenInterface pDevice = %x\n", pDevice));
Status = SdBusOpenInterface(
pDevice,//Adapter->PhyDeviceObject,//Adapter->hDevice,//UnderlyingPDO
&Adapter->SdBusIfStd,
sizeof(SDBUS_INTERFACE_STANDARD),
SDBUS_INTERFACE_VERSION);
KdPrint( ("SdBusOpenInterface() Status = %x\n", Status));
KdPrint( ("SdBusOpenInterface() size = %x\n ver = %x\nContext =
%x\n",
Adapter->SdBusIfStd.Size,
Adapter->SdBusIfStd.Version,
Adapter->SdBusIfStd.Context));
KdPrint( ("SdBusOpenInterface() interfRefer =
%x\nInitializeInterface = %x\nAcknowledgeInt = %x\n",
Adapter->SdBusIfStd.InterfaceReference,
Adapter->SdBusIfStd.InitializeInterface,
Adapter->SdBusIfStd.AcknowledgeInterrupt));

if(NT_SUCCESS(Status)) {
SDBUS_INTERFACE_PARAMETERS interfaceParameters = {0};
interfaceParameters.Size = sizeof(SDBUS_INTERFACE_PARAMETERS);
interfaceParameters.TargetObject =
Adapter->LowerDeviceObject;//Adapter->TargetObject;
interfaceParameters.DeviceGeneratesInterrupts = FALSE;//TRUE;
interfaceParameters.CallbackAtDpcLevel = TRUE;//if TRUE,low latency time
of interrupt delivery
//callback will be entered at DPC level,FALSE,at passive level.
//interfaceParameters.CallbackRoutine =
MrvEventCallback;//pMyDriverCallback;
KdPrint(("SdBusOpenInterface() success\n"));
//Status = STATUS_UNSUCCESSFUL;
KdPrint(("before SdBusIfStd.InitializeInterface() Status =
%x\n",Status));

//Status = STATUS_SUCCESS;
if(Adapter->SdBusIfStd.InitializeInterface) {
Status = (Adapter->SdBusIfStd.InitializeInterface)(
Adapter->SdBusIfStd.Context,
&interfaceParameters);

if(NT_SUCCESS(Status)) {
KdPrint(("SdBusIfStd.InitializeInterface() success\n"));
}//if
else
KdPrint(("SdBusIfStd.InitializeInterface() failed
Status = %x\n",Status));
}//if
}//if
else
KdPrint(("SdBusOpenInterface() failed\n"));

"Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:uvGTK3nYFHA.3272@TK2MSFTNGP14.phx.gbl...
> there is probably something wrong about your card. The SD bus is a pnp
> bus, it will auto detect your card upon insertion.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "iwub" <iwub@etang.com> wrote in message
> news:OTBkC9dYFHA.2128@TK2MSFTNGP14.phx.gbl...
>> Then how to let the system know I insert the device?
>> the system did not find the device insert when I insert the SDIO card.
>>
>>
>> the HW ID is correct. I think.
>>
>>
>> "Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
>>> yes. you must let the system find the device and your INF must match the
>>> SDBUS hardware ID generated for your device.
>>>
>>> d
>>>
>>> --
>>> Please do not send e-mail directly to this alias. this alias is for
>>> newsgroup purposes only.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>> "iwub" <iwub@etang.com> wrote in message
>>> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>>>> the driver is intalled by hand, it is not detected by host.(is it the
>>>> device problem?)
>>>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>>>> driver).
>>>> what will hanppen then? the device must be find by system itself?
>>>>
>>>> thanks
>>>>
>>>> "Pavel A." <pavel_a@NOwritemeNO.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>>>> Your driver is installed for the SD device ID, it isn't root
>>>>> enumerated?
>>>>> NdisMGetDeviceProperty returns valid pointer in
>>>>> Adapter->PhyDeviceObject ?
>>>>>
>>>>> --PA
>>>>>
>>>>> "iwub" wrote:
>>>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>>>> all
>>>>>> the time,I have no idea.
>>>>>> please help me, if you know this.
>>>>>>
>>>>>> and it said, SD function drivers are WDM drivers that are linked to
>>>>>> the SD
>>>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>>>> How to understand it?who can explain for me. thanks!
>>>>>>
>>>>>> THX very much!
>>>>>>
>>>>>> AMon
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

iwub
Fri May 27 04:51:24 CDT 2005

Yes, I am sure that our card is wrong.
but why sometimes it can be find by system?
By now, the device is detected by system just twice, you know, I test more
than 100 hundred.
THX

"Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:uvGTK3nYFHA.3272@TK2MSFTNGP14.phx.gbl...
> there is probably something wrong about your card. The SD bus is a pnp
> bus, it will auto detect your card upon insertion.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "iwub" <iwub@etang.com> wrote in message
> news:OTBkC9dYFHA.2128@TK2MSFTNGP14.phx.gbl...
>> Then how to let the system know I insert the device?
>> the system did not find the device insert when I insert the SDIO card.
>>
>>
>> the HW ID is correct. I think.
>>
>>
>> "Doron Holan [MS]" <doronh@nospam.microsoft.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:%230u7M7PYFHA.616@TK2MSFTNGP12.phx.gbl...
>>> yes. you must let the system find the device and your INF must match the
>>> SDBUS hardware ID generated for your device.
>>>
>>> d
>>>
>>> --
>>> Please do not send e-mail directly to this alias. this alias is for
>>> newsgroup purposes only.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>> "iwub" <iwub@etang.com> wrote in message
>>> news:%23cKc1aMYFHA.3356@TK2MSFTNGP15.phx.gbl...
>>>> the driver is intalled by hand, it is not detected by host.(is it the
>>>> device problem?)
>>>> My device is intalled PCI-SDIO (sdbus.sys), SDIO device(my function
>>>> driver).
>>>> what will hanppen then? the device must be find by system itself?
>>>>
>>>> thanks
>>>>
>>>> "Pavel A." <pavel_a@NOwritemeNO.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:2448E027-9EFA-4E2A-8DA5-318875EF6F5C@microsoft.com...
>>>>> Your driver is installed for the SD device ID, it isn't root
>>>>> enumerated?
>>>>> NdisMGetDeviceProperty returns valid pointer in
>>>>> Adapter->PhyDeviceObject ?
>>>>>
>>>>> --PA
>>>>>
>>>>> "iwub" wrote:
>>>>>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
>>>>>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
>>>>>> callback routine , I call it in my MiniportInitialize(),but it failed
>>>>>> all
>>>>>> the time,I have no idea.
>>>>>> please help me, if you know this.
>>>>>>
>>>>>> and it said, SD function drivers are WDM drivers that are linked to
>>>>>> the SD
>>>>>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>>>>>> How to understand it?who can explain for me. thanks!
>>>>>>
>>>>>> THX very much!
>>>>>>
>>>>>> AMon
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

iwub
Thu Jun 02 20:51:43 CDT 2005

Hi,
everyone, 3 points,
1, My card is wrong. It can use now although it can not detected by system
itself.
2, register is wrong cause I have setup with a different PID&VID, so it is
report a different adapter when I reboot machine.
3, I do not do well in deregister the open interface, So it is wrong at the
second initialization.

Now it can be opened and initialized OK.

THANKS,

"iwub" <iwub@etang.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:OR5OPYEYFHA.580@TK2MSFTNGP15.phx.gbl...
> the sdbusapi.doc said, the SdBusOpenInterface() should be called in
> AddDevice(), but I develop a driver for NDIS NIC, then I have no this
> callback routine , I call it in my MiniportInitialize(),but it failed all
> the time,I have no idea.
> please help me, if you know this.
>
> and it said, SD function drivers are WDM drivers that are linked to the SD
> bus driver lib.they are not minport driver like NDIS or SCSI driver.
> How to understand it?who can explain for me. thanks!
>
> THX very much!
>
> AMon
>

iwub
Thu Jun 09 20:33:21 CDT 2005

This is a multi-part message in MIME format.

------=_NextPart_000_002B_01C56D9F.716FB0E0
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Who knows why SdSubmitRequest() not correct?

I download my firmware, and return one ChipID for download further =
information.
But the return is not correct although it response successful.
the return data is also be 0 10 0 0
or 0 20 0 0 .
Thanks,
=20

00000004 1.55989323 =3D=3D=3D=3D> DriverEntry=20
00000005 1.55990273 --- NDIS Version(5.1) ---=20
00000006 1.55990692 Calling NdisMRegisterMiniport...=20
00000007 1.55991753 <=3D=3D DriverEntry: Sychip Shanghai register =
miniport success=20
00000008 1.55992200 <=3D=3D=3D=3D DriverEntry, Status =3D 0x0 =20
00000009 1.55992340 =20
00000010 1.77511276 =3D=3D=3D=3D> MrvDrvInitialize=20
00000011 1.77512896 MrvDrvInitialize : Adapter =3D 81e87000=20
00000012 1.77513455 MrvDrvInitialize : Adapter->MrvDrvAdapterHdl =3D =
8247f130=20
00000013 1.77514014 MrvDrvInitialize : Adapter->ConfigurationHandle =3D =
f8acb914=20
00000014 1.77514544 MrvDrvInitialize : =
Adapter->WrapperConfigurationContext =3D f8acb914=20
00000015 1.77515075 =3D=3D=3D=3D> MrvDrvInitialize =
NdisMSetAttributesEx()=20
00000016 1.77732952 NicFindAdapter() -----> =20
00000017 1.77733930 NdisMGetDeviceProperty() =20
00000018 1.77734070 Adapter =3D 8247f130,=20
00000019 1.77734209 PDO =3D 82e9c960,=20
00000020 1.77734349 FDO =3D 8247f030,=20
00000021 1.77734489 LDO =3D 82e9c960=20
00000022 1.77734991 SdBusOpenInterface pDevice =3D 82e9c960=20
00000023 1.77736332 SdBusOpenInterface() Status =3D 0=20
00000024 1.77736891 SdBusOpenInterface() size =3D 0=20
00000025 1.77737031 ver =3D 0=20
00000026 1.77737198 Context =3D 82dd99e0=20
00000027 1.77738009 SdBusOpenInterface() ---interfReference =3D f810e4f0 =

00000028 1.77738148 interfDereference =3D f810e522=20
00000029 1.77738316 InitializeInterface =3D f811775c=20
00000030 1.77738456 AcknowledgeInt =3D f810e776=20
00000031 1.77738847 SdBusOpenInterface() success=20
00000032 1.77739377 before SdBusIfStd.InitializeInterface() Status =3D =
c0000001=20
00000033 1.77740020 SdBusIfStd.InitializeInterface() success=20
00000034 1.77740551 ExAllocatePool() *sdrp =3D 82c37f78=20
00000035 1.77741361 SdBusSubmitRequest() success, FunctionNumber =3D =
f8acb684, 1=20
00000036 1.77741752 NicFindAdapter() <----- =20
00000037 1.77747172 >SdioCommand52 Write=20
00000038 1.77747563 SdioCommand52() ------>=20
00000039 1.77752508 SdioCommand52: SdBusSubmitRequest() 2 success =
Information =3D (null)=20
00000040 1.77753011 SdioCommand52:SdBusSubmitRequest() 2 success =
sdrp->ResponseLength =3D 4=20
00000041 1.77753485 SdioCommand52() <------Status =3D 0 =20
00000042 1.77753904 SDIO_ReadWriteDirect 0=20
00000043 1.77754324 INIT - Downloading Helper...=20
00000044 1.77754826 GetHelper()----helper_image[4] =3D 2, Len =3D 810=20
00000045 1.77755273 helper =3D 2, helper_len =3D 810=20
00000046 1.77755916 >SDIO_FirmwareDownload_WBL: Download start, FW size =
=3D 2064 bytes, block size=3D508 bytes=20
00000047 1.77756614 >SDIO_FirmwareDownload_WBL: Download , =
DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508 bytes=20
00000048 1.78792081 >SdioCommand53 Write addr=3D10000 blen=3D32 =
nblk=3D16 - irql =3D 0.=20
00000049 1.78800183 SdBusSubmitRequest() 3 success=20
00000050 1.78806413 SdBusSubmitRequest() 3 success=20
00000051 1.78812587 SdBusSubmitRequest() 3 success=20
00000052 1.78818705 SdBusSubmitRequest() 3 success=20
00000053 1.78824851 SdBusSubmitRequest() 3 success=20
00000054 1.78830997 SdBusSubmitRequest() 3 success=20
00000055 1.78837115 SdBusSubmitRequest() 3 success=20
00000056 1.78843261 SdBusSubmitRequest() 3 success=20
00000057 1.78849547 SdBusSubmitRequest() 3 success=20
00000058 1.78855748 SdBusSubmitRequest() 3 success=20
00000059 1.78861950 SdBusSubmitRequest() 3 success=20
00000060 1.78868068 SdBusSubmitRequest() 3 success=20
00000061 1.78874214 SdBusSubmitRequest() 3 success=20
00000062 1.78880416 SdBusSubmitRequest() 3 success=20
00000063 1.78886562 SdBusSubmitRequest() 3 success=20
00000064 1.78893127 SdBusSubmitRequest() 3 success=20
00000065 1.78893630 SDIO_FirmwareDownload_WBL: FW block #1=20
00000066 1.78894329 >SDIO_FirmwareDownload_WBL: Download , =
DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508 bytes=20
00000067 1.79963822 >SdioCommand53 Write addr=3D10000 blen=3D32 =
nblk=3D16 - irql =3D 0.=20
00000068 1.79971449 SdBusSubmitRequest() 3 success=20
00000069 1.79977707 SdBusSubmitRequest() 3 success=20
00000070 1.79983937 SdBusSubmitRequest() 3 success=20
00000071 1.79990110 SdBusSubmitRequest() 3 success=20
00000072 1.79996257 SdBusSubmitRequest() 3 success=20
00000073 1.80002403 SdBusSubmitRequest() 3 success=20
00000074 1.80008549 SdBusSubmitRequest() 3 success=20
00000075 1.80014750 SdBusSubmitRequest() 3 success=20
00000076 1.80020952 SdBusSubmitRequest() 3 success=20
00000077 1.80027098 SdBusSubmitRequest() 3 success=20
00000078 1.80033217 SdBusSubmitRequest() 3 success=20
00000079 1.80039446 SdBusSubmitRequest() 3 success=20
00000080 1.80045648 SdBusSubmitRequest() 3 success=20
00000081 1.80051850 SdBusSubmitRequest() 3 success=20
00000082 1.80058052 SdBusSubmitRequest() 3 success=20
00000083 1.80064310 SdBusSubmitRequest() 3 success=20
00000084 1.80064813 SDIO_FirmwareDownload_WBL: FW block #2=20
00000085 1.80065567 >SDIO_FirmwareDownload_WBL: Download , =
DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508 bytes=20
00000086 1.81135256 >SdioCommand53 Write addr=3D10000 blen=3D32 =
nblk=3D16 - irql =3D 0.=20
00000087 1.81141402 SdBusSubmitRequest() 3 success=20
00000088 1.81147548 SdBusSubmitRequest() 3 success=20
00000089 1.81153694 SdBusSubmitRequest() 3 success=20
00000090 1.81159896 SdBusSubmitRequest() 3 success=20
00000091 1.81166014 SdBusSubmitRequest() 3 success=20
00000092 1.81172272 SdBusSubmitRequest() 3 success=20
00000093 1.81178446 SdBusSubmitRequest() 3 success=20
00000094 1.81184648 SdBusSubmitRequest() 3 success=20
00000095 1.81190850 SdBusSubmitRequest() 3 success=20
00000096 1.81196996 SdBusSubmitRequest() 3 success=20
00000097 1.81203198 SdBusSubmitRequest() 3 success=20
00000098 1.81209400 SdBusSubmitRequest() 3 success=20
00000099 1.81215546 SdBusSubmitRequest() 3 success=20
00000100 1.81221747 SdBusSubmitRequest() 3 success=20
00000101 1.81227893 SdBusSubmitRequest() 3 success=20
00000102 1.81234654 SdBusSubmitRequest() 3 success=20
00000103 1.81235129 SDIO_FirmwareDownload_WBL: FW block #3=20
00000104 1.81235800 >SDIO_FirmwareDownload_WBL: Download , =
DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508 bytes=20
00000105 1.82307444 >SdioCommand53 Write addr=3D10000 blen=3D32 =
nblk=3D16 - irql =3D 0.=20
00000106 1.82315099 SdBusSubmitRequest() 3 success=20
00000107 1.82321356 SdBusSubmitRequest() 3 success=20
00000108 1.82327558 SdBusSubmitRequest() 3 success=20
00000109 1.82333760 SdBusSubmitRequest() 3 success=20
00000110 1.82339878 SdBusSubmitRequest() 3 success=20
00000111 1.82346024 SdBusSubmitRequest() 3 success=20
00000112 1.82352170 SdBusSubmitRequest() 3 success=20
00000113 1.82358289 SdBusSubmitRequest() 3 success=20
00000114 1.82364518 SdBusSubmitRequest() 3 success=20
00000115 1.82370720 SdBusSubmitRequest() 3 success=20
00000116 1.82376838 SdBusSubmitRequest() 3 success=20
00000117 1.82382984 SdBusSubmitRequest() 3 success=20
00000118 1.82389214 SdBusSubmitRequest() 3 success=20
00000119 1.82395416 SdBusSubmitRequest() 3 success=20
00000120 1.82401618 SdBusSubmitRequest() 3 success=20
00000121 1.82407988 SdBusSubmitRequest() 3 success=20
00000122 1.82408490 SDIO_FirmwareDownload_WBL: FW block #4=20
00000123 1.82409189 >SDIO_FirmwareDownload_WBL: Download , =
DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D32 bytes=20
00000124 1.83479493 >SdioCommand53 Write addr=3D10000 blen=3D32 nblk=3D2 =
- irql =3D 0.=20
00000125 1.83487762 SdBusSubmitRequest() 3 success=20
00000126 1.83494159 SdBusSubmitRequest() 3 success=20
00000127 1.83494662 SDIO_FirmwareDownload_WBL: FW block #5=20
00000128 1.84553037 >SdioCommand53 Write addr=3D10000 blen=3D32 nblk=3D1 =
- irql =3D 0.=20
00000129 1.84559239 SdBusSubmitRequest() 3 success=20
00000130 1.85627475 Download helper file fwStatus =3D 3=20
00000131 1.85628201 >SDIO_WaitForHelper: Waiting for helper=20
00000132 1.85628704 >SDIO_WaitForHelper: Waiting for helper retry =3D =
1387=20
00000133 1.85629123 >SdioCommand52 Read=20
00000134 1.85629514 SdioCommand52() ------>=20
00000135 1.85635102 SdioCommand52: SdBusSubmitRequest() 2 success =
Information =3D (null)=20
00000136 1.85635632 SdioCommand52:SdBusSubmitRequest() 2 success =
sdrp->ResponseLength =3D 4=20
00000137 1.85636163 SdioCommand52:SdBusSubmitRequest() 2 success =
*pValue =3D 10=20
00000138 1.85636694 sdrp->ResponseData.AsUCHAR =3D bf 10 0 0 =20
00000139 1.85640996 SdioCommand52: SdBusSubmitRequest() 2 success =
Information =3D (null)=20
00000140 1.85641527 SdioCommand52:SdBusSubmitRequest() 2 success =
sdrp->ResponseLength =3D 4=20
00000141 1.85642002 SdioCommand52:SdBusSubmitRequest() 2 success =
*pValue =3D 10=20
00000142 1.85642505 sdrp->ResponseData.AsUCHAR =3D bf 10 0 0 =20
00000143 1.85642980 SdioCommand52() <------Status =3D 0 =20
00000144 1.85643455 >SDIO_WaitForHelper: Waiting for helper OK 1010=20
00000145 1.85643874 Download helper file OK=20
00000146 1.85644265 Older version helper: no chipId.=20
00000147 1.85644712 <=3D=3D=3D=3D MrvDrvInitialize Sychip Shanghai =20

"iwub" <iwub@etang.com> =
=D0=B4=C8=EB=CF=FB=CF=A2=D0=C2=CE=C5:eoq9679ZFHA.3492@TK2MSFTNGP14.phx.gb=
l...
> Hi,
> everyone, 3 points,
> 1, My card is wrong. It can use now although it can not detected by =
system=20
> itself.
> 2, register is wrong cause I have setup with a different PID&VID, so =
it is=20
> report a different adapter when I reboot machine.
> 3, I do not do well in deregister the open interface, So it is wrong =
at the=20
> second initialization.
>=20
>=20
> Now it can be opened and initialized OK.
>=20
>=20
> THANKS,
>=20
>=20
>=20
> "iwub" <iwub@etang.com> =
=D0=B4=C8=EB=CF=FB=CF=A2=D0=C2=CE=C5:OR5OPYEYFHA.580@TK2MSFTNGP15.phx.gbl=
...
>> the sdbusapi.doc said, the SdBusOpenInterface() should be called in=20
>> AddDevice(), but I develop a driver for NDIS NIC, then I have no this =

>> callback routine , I call it in my MiniportInitialize(),but it failed =
all=20
>> the time,I have no idea.
>> please help me, if you know this.
>>
>> and it said, SD function drivers are WDM drivers that are linked to =
the SD=20
>> bus driver lib.they are not minport driver like NDIS or SCSI driver.
>> How to understand it?who can explain for me. thanks!
>>
>> THX very much!
>>
>> AMon
>>=20
>=20
>
------=_NextPart_000_002B_01C56D9F.716FB0E0
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>Who knows why SdSubmitRequest() not =
correct?</DIV>
<DIV> </DIV>
<DIV>I download my firmware, and return one ChipID for =
download=20
further information.</DIV>
<DIV>But the return is not correct although it response=20
successful.</DIV>
<DIV>the return data is also be 0 10 0 0</DIV>
<DIV>or 0 20 0 0 .</DIV>
<DIV>Thanks,</DIV>
<DIV>  </DIV>
<DIV> </DIV>
<DIV>00000004 1.55989323 =3D=3D=3D=3D> =
DriverEntry=20
 00000005 1.55990273 --- NDIS Version(5.1)=20
---  00000006 1.55990692 Calling=20
NdisMRegisterMiniport...  00000007 1.55991753 <=3D=3D=
=20
DriverEntry:  Sychip Shanghai register miniport=20
success  00000008 1.55992200 <=3D=3D=3D=3D =
DriverEntry, Status =3D=20
0x0   00000009 1.55992340 =20
  00000010 1.77511276 =3D=3D=3D=3D> =
MrvDrvInitialize=20
 00000011 1.77512896 MrvDrvInitialize : Adapter =3D=20
81e87000  00000012 1.77513455 MrvDrvInitialize :=20
Adapter->MrvDrvAdapterHdl =3D=20
8247f130  00000013 1.77514014 MrvDrvInitialize :=20
Adapter->ConfigurationHandle =3D=20
f8acb914  00000014 1.77514544 MrvDrvInitialize :=20
Adapter->WrapperConfigurationContext =3D=20
f8acb914  00000015 1.77515075 =3D=3D=3D=3D> =
MrvDrvInitialize=20
NdisMSetAttributesEx()  00000016 1.77732952 NicFindAdap=
ter()=20
----->=20
  00000017 1.77733930 NdisMGetDeviceProperty() &nb=
sp;=20
  00000018 1.77734070 Adapter =3D=20
8247f130,  00000019 1.77734209 PDO =3D=20
82e9c960,  00000020 1.77734349 FDO =3D=20
8247f030,  00000021 1.77734489 LDO =3D=20
82e9c960  00000022 1.77734991 SdBusOpenInterface =
pDevice =3D=20
82e9c960  00000023 1.77736332 SdBusOpenInterface() =
Status =3D=20
0  00000024 1.77736891 SdBusOpenInterface() size =3D=20
0  00000025 1.77737031  ver =3D=20
0  00000026 1.77737198 Context =3D=20
82dd99e0  00000027 1.77738009 SdBusOpenInterface()=20
---interfReference =3D=20
f810e4f0  00000028 1.77738148 interfDereference =3D=20
f810e522  00000029 1.77738316 InitializeInterface =3D=20
f811775c  00000030 1.77738456 AcknowledgeInt =3D=20
f810e776  00000031 1.77738847 SdBusOpenInterface()&nbsp=
;=20
success  00000032 1.77739377 before=20
SdBusIfStd.InitializeInterface() Status =3D=20
c0000001  00000033 1.77740020 SdBusIfStd.InitializeInte=
rface() =20
success  00000034 1.77740551 ExAllocatePool()  =
*sdrp =3D=20
82c37f78  00000035 1.77741361 SdBusSubmitRequest()&nbsp=
;=20
success, FunctionNumber =3D f8acb684,=20
1  00000036 1.77741752 NicFindAdapter() <-----=20
  00000037 1.77747172 >SdioCommand52=20
Write  00000038 1.77747563 SdioCommand52() =20
------>  00000039 1.77752508 SdioCommand52:=20
SdBusSubmitRequest()  2 success  Information =3D=20
(null)  00000040 1.77753011 SdioCommand52:SdBusSubmitRe=
quest() =20
2 success  sdrp->ResponseLength =3D=20
4  00000041 1.77753485 SdioCommand52()  =
<------Status=20
=3D 0   00000042 1.77753904 SDIO_ReadWriteDirect=20
0  00000043 1.77754324 INIT - Downloading=20
Helper...  00000044 1.77754826 GetHelper()----helper_im=
age[4]=20
=3D 2, Len =3D 810  00000045 1.77755273 helper =3D 2, =
helper_len =3D=20
810  00000046 1.77755916 >SDIO_FirmwareDownload_WBL:=
=20
Download start, FW size =3D 2064 bytes, block size=3D508=20
bytes  00000047 1.77756614 >SDIO_FirmwareDownload_WB=
L:=20
Download , DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508=20
bytes  00000048 1.78792081 >SdioCommand53 Write =
addr=3D10000=20
blen=3D32 nblk=3D16 - irql =3D=20
0.  00000049 1.78800183 SdBusSubmitRequest()  3=20
success  00000050 1.78806413 SdBusSubmitRequest() =
3=20
success  00000051 1.78812587 SdBusSubmitRequest() =
3=20
success  00000052 1.78818705 SdBusSubmitRequest() =
3=20
success  00000053 1.78824851 SdBusSubmitRequest() =
3=20
success  00000054 1.78830997 SdBusSubmitRequest() =
3=20
success  00000055 1.78837115 SdBusSubmitRequest() =
3=20
success  00000056 1.78843261 SdBusSubmitRequest() =
3=20
success  00000057 1.78849547 SdBusSubmitRequest() =
3=20
success  00000058 1.78855748 SdBusSubmitRequest() =
3=20
success  00000059 1.78861950 SdBusSubmitRequest() =
3=20
success  00000060 1.78868068 SdBusSubmitRequest() =
3=20
success  00000061 1.78874214 SdBusSubmitRequest() =
3=20
success  00000062 1.78880416 SdBusSubmitRequest() =
3=20
success  00000063 1.78886562 SdBusSubmitRequest() =
3=20
success  00000064 1.78893127 SdBusSubmitRequest() =
3=20
success  00000065 1.78893630 SDIO_FirmwareDownload_WBL:=
FW=20
block =
#1  00000066 1.78894329 >SDIO_FirmwareDownload_WBL: =

Download , DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508=20
bytes  00000067 1.79963822 >SdioCommand53 Write =
addr=3D10000=20
blen=3D32 nblk=3D16 - irql =3D=20
0.  00000068 1.79971449 SdBusSubmitRequest()  3=20
success  00000069 1.79977707 SdBusSubmitRequest() =
3=20
success  00000070 1.79983937 SdBusSubmitRequest() =
3=20
success  00000071 1.79990110 SdBusSubmitRequest() =
3=20
success  00000072 1.79996257 SdBusSubmitRequest() =
3=20
success  00000073 1.80002403 SdBusSubmitRequest() =
3=20
success  00000074 1.80008549 SdBusSubmitRequest() =
3=20
success  00000075 1.80014750 SdBusSubmitRequest() =
3=20
success  00000076 1.80020952 SdBusSubmitRequest() =
3=20
success  00000077 1.80027098 SdBusSubmitRequest() =
3=20
success  00000078 1.80033217 SdBusSubmitRequest() =
3=20
success  00000079 1.80039446 SdBusSubmitRequest() =
3=20
success  00000080 1.80045648 SdBusSubmitRequest() =
3=20
success  00000081 1.80051850 SdBusSubmitRequest() =
3=20
success  00000082 1.80058052 SdBusSubmitRequest() =
3=20
success  00000083 1.80064310 SdBusSubmitRequest() =
3=20
success  00000084 1.80064813 SDIO_FirmwareDownload_WBL:=
FW=20
block =
#2  00000085 1.80065567 >SDIO_FirmwareDownload_WBL: =

Download , DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508=20
bytes  00000086 1.81135256 >SdioCommand53 Write =
addr=3D10000=20
blen=3D32 nblk=3D16 - irql =3D=20
0.  00000087 1.81141402 SdBusSubmitRequest()  3=20
success  00000088 1.81147548 SdBusSubmitRequest() =
3=20
success  00000089 1.81153694 SdBusSubmitRequest() =
3=20
success  00000090 1.81159896 SdBusSubmitRequest() =
3=20
success  00000091 1.81166014 SdBusSubmitRequest() =
3=20
success  00000092 1.81172272 SdBusSubmitRequest() =
3=20
success  00000093 1.81178446 SdBusSubmitRequest() =
3=20
success  00000094 1.81184648 SdBusSubmitRequest() =
3=20
success  00000095 1.81190850 SdBusSubmitRequest() =
3=20
success  00000096 1.81196996 SdBusSubmitRequest() =
3=20
success  00000097 1.81203198 SdBusSubmitRequest() =
3=20
success  00000098 1.81209400 SdBusSubmitRequest() =
3=20
success  00000099 1.81215546 SdBusSubmitRequest() =
3=20
success  00000100 1.81221747 SdBusSubmitRequest() =
3=20
success  00000101 1.81227893 SdBusSubmitRequest() =
3=20
success  00000102 1.81234654 SdBusSubmitRequest() =
3=20
success  00000103 1.81235129 SDIO_FirmwareDownload_WBL:=
FW=20
block =
#3  00000104 1.81235800 >SDIO_FirmwareDownload_WBL: =

Download , DownloadPkt.Buf =3D f8acb4d0 , DownloadPkt.Buf size=3D508=20
bytes  00000105 1.82307444 >SdioCommand53 Write =
addr=3D10000=20
blen=3D32 nblk=3D16 - irql =3D=20
0.  00000106 1.82315099 SdBusSubmitRequest()  3=20
success  00000107 1.82321356 SdBusSubmitRequest() =
3=20
success  00000108 1.82327558 SdBusSubmitRequest() =
3=20
success  00000109 1.82333760 SdBusSubmitRequest() =
3=20
success  00000110 1.82339878 SdBusSubmitRequest() =
3=20
success  00000111 1.82346024 SdBusSubmitRequest() =
3=20
success  00000112 1.82352170 SdBusSubmitRequest() =
3=20
success  00000113 1.82358289 SdBusSubmitRequest() =
3=20
success  00000114 1.82364518 SdBusSubmitRequest() =
3=20
success  00000115 1.82370720 SdBusSubmitRequest() =
3=20

about SdBusOpenInterface() and SDIO

RE: about SdBusOpenInterface() and SDIO by pavel_a

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by Doron

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by Doron

Re: about SdBusOpenInterface() and SDIO by Maxim

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by Doron

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdBusOpenInterface() and SDIO by iwub

Re: about SdSubmitRequest() and SDIO by iwub