From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: what config setting causes barebox to automount the boot partition?
Date: Thu, 9 Feb 2012 08:21:00 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202090818140.27245@oneiric> (raw)
In-Reply-To: <20120209140238.49a3863b@eb-e6520>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1307 bytes --]
On Thu, 9 Feb 2012, Eric Bénard wrote:
> Le Thu, 9 Feb 2012 06:54:40 -0500 (EST),
> "Robert P. J. Day" <rpjday@crashcourse.ca> a écrit :
>
> >
> > i just noticed with my panda build that the boot partition of the SD
> > card is automatically mounted under "boot". i don't remember that
> > happening with my beagle, and i'm not sure if i messed with the config
> > settings before building for the panda.
> >
> > what is it that generates that mount? thanks.
> >
> panda/board.c
> mkdir ("/boot", 0666);
> ret = mount(diskdev, "fat", "/boot");
> if (ret) {
> printf("failed to mount %s\n", diskdev);
> return 0;
> }
oh, my, i can see there's much work to do as the beagle board.c file
does nothing equivalent. i thought it was just a config setting of
some kind, now i see that there's definitely some coding to be done.
thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-02-09 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 11:54 Robert P. J. Day
2012-02-09 13:02 ` Eric Bénard
2012-02-09 13:21 ` Robert P. J. Day [this message]
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=alpine.DEB.2.02.1202090818140.27245@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.com \
/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