Hi,
I'm developing a SDIO card driver for wince5, I face a problem
about the SDIO CCCR spec version. the CCCR spec version of our SDIO
card is 1.2. But in SDBUS driver, it only read the power control
register when the CCCR spec version is 1.1.( in shared code
Sddevice.cpp, line 1809, and sdhceventhandlers.cpp line 553). So in
our case, it won't read the power control register and the card
initialization will fail. I believe this is a bug in windows CE
driver. I modify that two line and my card can work correctly.
Here my doubt is that whether MS have a offical fix for this issue,
because I'm afraid if the bug exist in the commerical product, then my
SDIO card won't work. Is there anybody face this problem before?

Best Regards
Liu7290

Re: SDIO CCCR register version bug. by Ming

Ming
Mon Apr 14 07:12:16 PDT 2008

On Apr 14, 6:33 am, "liutao.p...@gmail.com" <liutao.p...@gmail.com>
wrote:
> Hi,
> I'm developing a SDIO card driver for wince5, I face a problem
> about the SDIO CCCR spec version. the CCCR spec version of our SDIO
> card is 1.2. But in SDBUS driver, it only read the power control
> register when the CCCR spec version is 1.1.( in shared code
> Sddevice.cpp, line 1809, and sdhceventhandlers.cpp line 553). So in
> our case, it won't read the power control register and the card
> initialization will fail. I believe this is a bug in windows CE
> driver. I modify that two line and my card can work correctly.
> Here my doubt is that whether MS have a offical fix for this issue,
> because I'm afraid if the bug exist in the commerical product, then my
> SDIO card won't work. Is there anybody face this problem before?
>
> Best Regards
> Liu7290

Is this really a "bug" in Windows CE 5? Or did the designers just
simply only designed CE5 to be compliant to 1.1? Have you installed
all the QFEs? Other than that since you did get the driver to work by
modifying the code in the public folder couldn't you just make create
a copy of the source files for the SDBus library (library will not be
located in Public), create a new library based on the SDBus library
with the 2 lines modified and simply point your SDIO card driver to
the new library?

Also please do not make the same post on multiple newsgroups. Thanks.

Regards,
Ming Wang

Re: SDIO CCCR register version bug. by liu7290

liu7290
Wed Apr 16 09:13:55 PDT 2008

The point here is for commerical product of my SDIO card, I will only
provide
client driver, I should not provide sdbus driver. So if this problem
exist in the
sdbus driver of a commerical product, then my SDIO card won't work.

because that may cause
On Apr 14, 4:12 pm, Ming Wang <wange...@gmail.com> wrote:
> On Apr 14, 6:33 am, "liutao.p...@gmail.com" <liutao.p...@gmail.com>
> wrote:
>
> > Hi,
> > I'm developing a SDIO card driver for wince5, I face a problem
> > about the SDIO CCCR spec version. the CCCR spec version of our SDIO
> > card is 1.2. But in SDBUS driver, it only read the power control
> > register when the CCCR spec version is 1.1.( in shared code
> > Sddevice.cpp, line 1809, and sdhceventhandlers.cpp line 553). So in
> > our case, it won't read the power control register and the card
> > initialization will fail. I believe this is a bug in windows CE
> > driver. I modify that two line and my card can work correctly.
> > Here my doubt is that whether MS have a offical fix for this issue,
> > because I'm afraid if the bug exist in the commerical product, then my
> > SDIO card won't work. Is there anybody face this problem before?
>
> > Best Regards
> > Liu7290
>
> Is this really a "bug" in Windows CE 5? Or did the designers just
> simply only designed CE5 to be compliant to 1.1? Have you installed
> all the QFEs? Other than that since you did get the driver to work by
> modifying the code in the public folder couldn't you just make create
> a copy of the source files for the SDBus library (library will not be
> located in Public), create a new library based on the SDBus library
> with the 2 lines modified and simply point your SDIO card driver to
> the new library?
>
> Also please do not make the same post on multiple newsgroups. Thanks.
>
> Regards,
> Ming Wang