With my recent effort to move all my remaining 3.4 machines to
(almost)mainline, I saw a strange pattern:
Many of the SD cards I have can't be read by U-boot. Yet, they work
fine elsewhere.
More specifically, more than half of the SD cards I've tried show the
following behavior:
- I can put U-boot on them and the A20 boots fine.
- The U-boot code loaded from the card (mainline U-boot 2014-07) can
read the card's partition table, root directory, and load the
boot.scr script.
- Once booted, Linux can read all the files on the card via
/dev/mmcblk0p1.
- All 3 USB card readers I have can read&write to those cards without
any problem.
- But U-boot can't load the vmlinuz/uImage files (I get ext4 errors).
IIUC there's a general sentiments that most SD cards are crap (and
indeed mine are all old&cheap), but I find it striking that they work
"everywhere" *except* for U-boot reading a large file.
Of course, this problem pushed me to change my machines's setup so
U-boot reads the kernel&initrd directly from the hard-disk, so to some
extent I don't care that much about it any more, but still. I think the
MMC code used in our U-boot has a bug.
Stefan
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
