public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Frank Pagliughi <fpagliughi@mindspring.com>
To: Frank Pagliughi <fpagliughi@mindspring.com>
Cc: Nick Garnett <nickg@ecoscentric.com>,  ecos-devel@ecos.sourceware.org
Subject: Re: Partition support for FAT file system
Date: Wed, 18 Jun 2008 19:28:00 -0000	[thread overview]
Message-ID: <485961D4.5000804@mindspring.com> (raw)
In-Reply-To: <48593F4C.7000808@mindspring.com>


>>
>> This is already handled in the io/disk package. You mount /dev/diskN/M
>> for partition M of disk N and /dev/diskN/0 for the whole disk.
>> Partitioning is independent of filesystem type, so it must be done at
>> a lower level that the FATFS.
>>
>>   
> Ah, ok, thanks, Nick. I misunderstood that terminology in the IDE 
> case, mistaking it as 'N' for the controller and 'M' for the disk on 
> that controller. This makes sense.
>
> 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?
Nevermind. I found my mistake....

The name of the disk should end with a slash, like "/dev/disk0/", and 
then the lookup functionality in the disk library scans for partitions. 
I had left off the final slash and then cyg_io_lookup() was failing the 
exact match.

Thanks again for the help,
Frank

      parent reply	other threads:[~2008-06-18 19:28 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
2008-06-18 19:28               ` Frank Pagliughi [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=485961D4.5000804@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).