mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "George Pontis" <GPontis@z9.com>
To: barebox@lists.infradead.org
Subject: Lost access to M25Pxx in move to 2013.01
Date: Sat, 2 Feb 2013 08:35:39 -0800	[thread overview]
Message-ID: <009d01ce0163$5629e7a0$027db6e0$@com> (raw)

Under 2012.11 I created a new board support package for custom hardware,
which included a M25P32. I store barebox and its environment there, and boot
from it. The board file also defines partitions for it. The first three look
like this:

        devfs_add_partition("m25p0",        0, 0x050000,
DEVFS_PARTITION_FIXED, "barebox");
        devfs_add_partition("m25p0", 0x050000, 0x010000,
DEVFS_PARTITION_FIXED, "env0");
        devfs_add_partition("m25p0", 0x060000, 0x330000,
DEVFS_PARTITION_FIXED, "kernel");

This created devices /dev/barebox, /dev/env0, and so on. It also allowed for
simple commands like "erase /dev/barebox", "tftp barebox.bin /dev/barebox",
etc.

More recently I updated to the 2013.01 release. My config file is not much
different and it still has enabled CONFIG_MTD, CONFIG_MTD_M25P80,
CONFIG_MTD_WRITE. The new release starts up just fine and boots the kernel
as usual. However, it does not see the M25P32.

With the earlier release, I saw a line displayed at startup as so:

m25p m25p0: m25p32 (4096 Kbytes)

Also, devinfo listed the partitions on the part. That m25p line is not
displayed with the 2013.01 release and there are no partitions. Devinfo does
show one line for the m25p driver.

Any suggestions where to look for a fix ?



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2013-02-02 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 16:35 George Pontis [this message]
2013-02-02 17:56 ` Antony Pavlov
2013-02-02 18:09   ` Eric Bénard
2013-02-04 20:16   ` George Pontis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009d01ce0163$5629e7a0$027db6e0$@com' \
    --to=gpontis@z9.com \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox