OMAP2430sdp MMC driver for 2.6.21
Hi Sree,
I saw you enabled SD card successfully on OMAP2430sdp for 2.6.21 on linux-omap mailing list. Did you use the drivers posted by Khasim? Could you please share your patch or give me some hints? I also got the new git kernel, but I can't make SD card work well. I'm blocked here for two weeks. Following is my board's u-boot boot message:
U-Boot 1.1.4 (Sep 18 2006 - 16:46:43)
OMAP2430C-GP revision 3, PRCM #5A TI 2430SDP 0.1 Version + mDDR (Boot NOR)
DRAM: 128 MB Flash: 192 MB
Muxed OneNAND 128MB 1.8V 16-bit (0x30) Scanning device for bad blocks num of blocks = 2048
Bad eraseblock 120 at 0x00f00000
In: serial Out: serial Err: serial
OMAP243X SDP #
Thanks.
Best Regards,
Yang Shi
iPod、万 点 巨 额 点 卡、奖 学 金……海 量 奖 品,想 拿 就 拿!
Hi
I didnt used the patch sent by Khasim
I took the virtual Bus support from 2.6.14 kernel
and changed the mmc_2430sdp.c and omap_hsmmc.c as per the 2.6.21 kernel I will send the patch whenever I finished cleaning it..
thanks
sree
Quoted 32 lines · 石洋
Hi Sree,
I saw you enabled SD card successfully on OMAP2430sdp for 2.6.21 on linux-omap mailing list. Did you use the drivers posted by Khasim? Could you please share your patch or give me some hints? I also got the new git kernel, but I can't make SD card work well. I'm blocked here for two weeks. Following is my board's u-boot boot message:
U-Boot 1.1.4 (Sep 18 2006 - 16:46:43)
OMAP2430C-GP revision 3, PRCM #5A
TI 2430SDP 0.1 Version + mDDR (Boot NOR)
DRAM: 128 MB
Flash: 192 MB
Muxed OneNAND 128MB 1.8V 16-bit (0x30)
Scanning device for bad blocks
num of blocks = 2048
Bad eraseblock 120 at0x00f00000
In: serial
Out: serial
Err: serial
OMAP243X SDP #Thanks.
Best Regards,
Yang Shi------------------------------
iPod、万 点 巨 额 点 卡、奖 学 金……海 量 奖 品,想 拿 就 拿!
<http://event.mail.163.com/chanel/xyq_07summer.htm?from=126_NO8>
Signature · 3 lines
Sreedhar Sambangi MS in Electrical Engg San Diego State University
Hi,
this may be unrelated but I found that the (not so) recent change in mmc_omap_set_ios() broke SD support on OMAP310. I was digging into the driver maybe two month sago and found that the change made the MMC host send the init sequence to the card far too often during initialisation. Sending it only once or reverting the following commit:
made it work better. I haven't posted any information because I had to give up before I managed to make the driver work completely, like it did in 2.6.20. The issue of setting R1 response type instead of R6 and other issues are still unresolved.
Regards
Quoted 2 lines · andrzej zaborowski
Hi,
this may be unrelated but I found that the (not so) recent change in
Sorry, this turns out to be completely unrelated to this thread.