From: Frank Pagliughi <fpagliughi@mindspring.com>
To: Nick Garnett <nickg@ecoscentric.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Partition support for FAT file system
Date: Fri, 20 Jun 2008 13:56:00 -0000 [thread overview]
Message-ID: <485BB704.6050903@mindspring.com> (raw)
In-Reply-To: <m3myli4q79.fsf@xl5.calivar.com>
Nick Garnett wrote:
> Frank Pagliughi <fpagliughi@mindspring.com> writes:
>
>
>> So then it's the IDE driver that should scan the partition table on
>> the physical disk and export separate mount points for each? Would
>> that be the proper way to go?
>>
>
> No, the generic disk layer already does all of this. It reads the MBR
> from the disk, looks for a partition table and sets up its data
> structures accordingly.
>
> Take a look in io/disk/current/src/disk.c, specifically the read_mbr()
> and read_partition() functions. And the code in disk_lookup() which
> selects the right partition.
>
> In the same way that it shouldn't be done at too high a level,
> partitioning shouldn't be done at too low a level either. Partitions
> can exist on a wide variety of media, not just IDE disks.
>
>
>
By the way... The main reason I had trouble with this, is because the
one disk test application, fatfs1, doesn't work out of the box. The FAT
test uses disks named like "/dev/disk0/" whereas the IDE package
defaults to names like "/dev/hda/". Is one naming convention preferred
over the other? Should we change the default for one or the other?
- Frank
next prev parent reply other threads:[~2008-06-20 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 9:36 Strange buildsystem behaviour Lars Poeschel
2008-06-18 9:53 ` Andrew Lunn
2008-06-18 10:07 ` Lars Poeschel
2008-06-18 10:23 ` Andrew Lunn
2008-06-18 10:58 ` Lars Poeschel
2008-06-18 16:26 ` Partition support for FAT file system Frank Pagliughi
2008-06-18 16:44 ` Nick Garnett
2008-06-18 17:01 ` Frank Pagliughi
2008-06-18 19:26 ` Nick Garnett
2008-06-20 13:56 ` Frank Pagliughi [this message]
2008-06-18 19:28 ` Frank Pagliughi
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=485BB704.6050903@mindspring.com \
--to=fpagliughi@mindspring.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=nickg@ecoscentric.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).