On Sat, Aug 24, 2013 at 07:37:00AM -0400, Robert P. J. Day wrote:
> On Sat, 24 Aug 2013, Luka Perkov wrote:
>
> > On Sat, Aug 24, 2013 at 12:01:25AM -0400, Robert P. J. Day wrote:
> > > On Sat, 24 Aug 2013, Luka Perkov wrote:
> > > > /dev/mmcblk0 0x60000 0x2000 0x2000
> > >
> > > ah, there's the misunderstanding. i thought we were discussing
> > > how to be able to refer *directly* to the eMMC partition "boot1",
> > > as in /dev/mmcblk1boot1. it looks like what you're describing
> > > would refer instead simply to /dev/mmcblk1, correct?
>
> > Even though the config is actually refering to /dev/mmcblk1 in fact
> > it's writing/reading to /dev/mmcblk1p1 (or /dev/mmcblk1boot1) in
> > your case. But you need to configure it properly for your MMC
> > device.
>
> right, i can see that and that clarifies things for me. my
> *original* question was whether there was a way to set up
> /etc/fw_env.config to refer to the eMMC partition /dev/mmcblk1boot1
> *directly*, treating it as a regular block partition and bypassing all
> the MTD-related processing. (perhaps stefano can weigh in and say
> whether that's how he understood what i was asking.)
>
> if you instead refer to /dev/mmcblk1, as i understand it, you're
> just back to the standard MTD-based access, yes?
>
> anyway, sorry if i didn't explain myself clearly the first time.
AFAIK there is no fw_{printenv,setenv} support for MMC. Except if you
use the patches I pointed out. Somebody please correct me if I'm wrong.
Luka
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
