Thread: Time for an open maemo fork?
View Single Post
wmarone is offline wmarone
2011-03-11 , 17:51
Posts: 1,746 | Thanked: 2,100 times | Joined on Sep 2009
#48
Originally Posted by Funklord View Post
I like the wringing part.
Seriously, if they could twist them and have pennies(won,yen,yuan) fall out, they would.

By a shell interface I mean pipes, fifo, stdio or what ever might be appropriate. For example: mplayer slave mode.
Qt applications don't compile with support for that by default IIRC (for instance, printf() will execute but nothing will appear on the console unless you change how it is built.) I'm not sure why dbus appeared, but I'm guessing there are limitations in the methods you describe that necessitated it... can't say for sure.

I'm very interested to hear more if you have insight on the issues?
At what point? bootloader? linux?
For bootloader and kernel you have OneNAND devices (packaged with your RAM and installed on top of the SoC,) which still accept raw NAND commands. Generally, however, this is one or two devices set up in a certain fashion to act like one.

I always thought the MTD subsystem was extremely flexible, was thinking of learning how to develop a larger flash memory bus for an arm board.
It is quite flexible, but eMMC lets you hide all the NAND + FTL complexity behind a standard block interface and share a driver with your SD card. It also dodges the issue that a lot of filesystems geared towards raw NOR/NAND devices don't behave well on larger devices (more CPU, more RAM.)

Do you know why pure nand costs more than nand+ftl
No, I would have to go look it up. I suspect it may be due to sheer quantity.
 

The Following 2 Users Say Thank You to wmarone For This Useful Post: