Had no idea - just decided to do something about it as it didn't work. Now it 
does. I also wanted to fix other problems that I/anyone else hasn't yet faced.
My plans for Raspberry Pi go beyond installing OpenWRT on it- but it's not 
worth doing anything with it as long as it has problems with root fs media.
I also didn't just make a patch for mmc/sd/sdhc - as I didn't want to see any 
other problems as well and my previous tests with Raspberry PI running
ArchLinux - that uses this very same kernel with aufs.. Was a success. 
Although, I want a far lighter weight OS than Arch and don't want to start 
removing
bits from stock, that's why OpenWRT is way better for me, it just needs to 
work.. This patch makes sure it works.

On 2.12.2013, at 19:11, Florian Fainelli <flor...@openwrt.org> wrote:

> 2013/12/1 Oskari Rauta <oskari.ra...@gmail.com>:
>> Sorry for posting similar patches twice.. But decided to do it right this 
>> time.
>> 
>> OpenWRT's kernel for brcm2708/raspberry pi is partially broken. It runs, but 
>> not very well, biggest concern is mmc drivers that:
>> - cause errors
>> - root filesystem might suddenly go to read-only mode
>> - usually after filesystem has gone to read-only mode, something has went so 
>> wrong, that it never will, even after reboot/power-cycle, be writable again.
>> - worst case was when one of my SD cards rendered to totally usable. It 
>> wasn't anymore usable at all, couldn't be formatted, etc.. --> trash
>> 
>> And then there are some other issues that I haven't been facing. Anyway, 
>> all, or atleast almost all of these problems are fixed in a raspberry pi 
>> specific linux kernel available from official raspberry pi git at 
>> github.com/raspberrypi. To make this a bit harder, they don't provide a 
>> patch sets against vanilla kernel that we could choose from, what they have, 
>> is a full blown kernel source that has been modified/patched to suite rpi. I 
>> first tested their kernel by using external kernel root, and noticed that it 
>> works. Posted about it to the mailing-list as well: 
>> http://patchwork.openwrt.org/patch/4488/
>> 
>> Then I took a vanilla kernel and ran a git diff between vanilla and rpi 
>> kernel, to get patch set manually. Ofcourse OpenWRT has it's own patches for 
>> 3.12* as well, so it wasn't quite that simple, but after a few modifications 
>> to patch set, I managed to get it working. Also few configuration items for 
>> 3.12.2 were missing that I added. Anyway, this patch allows one to build a 
>> clean and working image for Raspberry Pi without kernel problems. Tested it 
>> and it's good. Finally. Please, add to trunk.
>> 
>> Oh, where's the patch? Not here, problem is that, patching that kernel to 
>> rpi-kernel.. Is 8 megabytes, so it's way too much that mailinglist should 
>> handle, therefore, I have put up a site that holds the patch.. It's URL is 
>> https://sites.google.com/site/variousopenwrt/rpi-patch
> 
> Did you know that the patches OpenWrt uses are directly extracted from
> the rpi-3.10.y branch? So maybe a rebase against their latest tree
> could have been enough to fix the MMC/SD issues are you seeing.
> 
> -- 
> Florian

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to