Date: Tue, 13 Oct 2015 09:11:51 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: mib0 flash partition TL-WDR3600 Message-ID: <CAJ-Vmo=gDkQ4vwf36jfxkbPYibLKsCYfZ9kXvN=tXwKDTRmgVQ@mail.gmail.com> In-Reply-To: <561D24D0.6090707@grosbein.net> References: <561ADF43.8080005@grosbein.net> <CAJ-VmomAxNkQm6zdcrdhUbRahEqOL0pB_dgVui9U2oFxp%2B5wMQ@mail.gmail.com> <561B682E.8060607@grosbein.net> <CAJ-Vmo=apNZ-5kdoO3psgrpOwo8T1qJjUmqPUgszv-t4xbkT0g@mail.gmail.com> <561D24D0.6090707@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
It doesn't; it dd's 64k chunks at a time and that causes an erase/write cycle. If yo'ure just expanding cfg then yeah, cfg_save will do it via dd. -a On 13 October 2015 at 08:35, Eugene Grosbein <eugen@grosbein.net> wrote: > On 13.10.2015 00:51, Adrian Chadd wrote: >> Yes. The bootloader doesn't care what you do as long as: >> >> * you don't overwrite uboot; >> * you don't ovewrite uboot-env if it exists; >> * you put the "uboot application" (ie, the kernel) in the right place >> (which on these devices is at the beginning of the usable flash area); >> and >> * don't ovewrite ART. >> >> Just make sure you erase the extra space before you write into it. :) > > I don't see how cfg_save erases flash before writing. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=gDkQ4vwf36jfxkbPYibLKsCYfZ9kXvN=tXwKDTRmgVQ>