On Aug 12, 2012, at 6:04 PM, shawn wrote:
On Sun, 2012-08-12 at 17:52 -0700, Rick Thomas wrote:
*) Presumably making the mtd partition starting at zero visible to
Linux will alter the names of the other mtd partitions. Is this
going
to cause any problems down the line? like, with the progra
On Sun, 2012-08-12 at 17:52 -0700, Rick Thomas wrote:
>
> *) Presumably making the mtd partition starting at zero visible to
> Linux will alter the names of the other mtd partitions. Is this
> going
> to cause any problems down the line? like, with the programs that
> write the kernel and
On Aug 12, 2012, at 3:35 PM, shawn wrote:
#my commandline:
# cat /proc/cmdline
console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rw
mtdparts=orion_nand:0x10@0x0(u-boot),0x40@0x10(uImage),
0x1fb0@0x50(rootfs) rw
man proc -> type "//proc/cmdline" -> hit [enter]
On Aug 11, 2012, at 6:17 PM, Eric Cooper wrote:
On Sun, Aug 12, 2012 at 01:08:41AM +, Clint Adams wrote:
On Sat, Aug 11, 2012 at 05:45:00PM -0700, Rick Thomas wrote:
How can I make sure that uboot will always use the system disk?
You could check both drives for the uImage etc. files and
The mtdparts kernel parameter is currently documented only in the
kernel source code (in drivers/mtd/cmdlinepart.c):
* The format for the command line is as follows:
*
* mtdparts=[; := :[,]
* where is the name from the "cat /proc/mtd"
* command
* := [@offset][][ro][lk]
* :
On Sun, 2012-08-12 at 15:29 -0700, Rick Thomas wrote:
> On Aug 12, 2012, at 12:22 AM, shawn wrote:
>
> > On Sat, 2012-08-11 at 23:47 -0700, Rick Thomas wrote:
> >> The "examples" directory for the uboot-envtools contains sample
> >> fw_env.config files for several machine types, but not one th
On Aug 12, 2012, at 12:22 AM, shawn wrote:
> On Sat, 2012-08-11 at 23:47 -0700, Rick Thomas wrote:
>> The "examples" directory for the uboot-envtools contains sample
>> fw_env.config files for several machine types, but not one that seems
>> to relate to my Marvell OpenRD "ultimate" box. Do
Re,
On Sun, Aug 12, 2012 at 04:38:02PM -0400, Chris Wilkinson wrote:
> Unfortunately this doesn't appear so since the kernel version number
> is embedded in paths within the initrd archive. If this doesn't
> match *exactly* the kernel version, modules are not found.
Yes, it's safer to regenerat
Unfortunately this doesn't appear so since the kernel version number is
embedded in paths within the initrd archive. If this doesn't match *exactly*
the kernel version, modules are not found.
Did you find a method to create an initrd based on the kernel version?
Chris
-Original Message-
On Fri, Aug 10, 2012 at 07:31:56PM +0200, Jeremiah Foster wrote:
> I've set up an armel chroot with debootstrap (great tool) and I've
> copied a qemu-static-arm binary into /usr/bin so I'm hoping that
> working in that chroot will speed things up a bit. But any other
> advice you may have would b
Hi David,
On Fri, Aug 10, 2012 at 3:39 PM, David Given wrote:
> If you're doing kernel development, qemu has one killer feature in that
> it's got gdb integration. You can, at any point, halt the emulated
> processor and debug what it's doing. Which means that when you get a
> mysterious triple
On 12/08/12 01:45, Rick Thomas wrote:
[...]
> A bit more than half the time, when I reboot the machine, uboot tries
> (and fails) to boot from the data disk. To be sure of a good reboot, I
> need to physically disconnect the data disk and re-plug it after the
> kernel is loaded but before the file
On Sat, 2012-08-11 at 23:47 -0700, Rick Thomas wrote:
> The "examples" directory for the uboot-envtools contains sample
> fw_env.config files for several machine types, but not one that seems
> to relate to my Marvell OpenRD "ultimate" box. Does anybody on this
> list have one?
>
> Given t
13 matches
Mail list logo
