public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001073] ROM FS do not allow to use FIS names as device name in mount.
Date: Thu, 11 Nov 2010 14:53:00 -0000	[thread overview]
Message-ID: <20101111145258.47B211518842@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001073-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001073

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ecos-patches@ecos.sourcewar
                   |                            |e.org, john@dallaway.org.uk
          Component|ROM filesystem              |Patches and contributions

--- Comment #2 from John Dallaway <john@dallaway.org.uk> 2010-11-11 14:52:55 GMT ---
Alexander, thank you for making a contribution.

Being able to reference a ROM filesystem via a FIS entry seems like a good idea
since this is a typical usage scenario and the feature would improve usability.
However, one could also argue that this is application-level glue and does not
belong in the ROM filesystem package.

Any comments from other maintainers?

If there is some consensus that the feature is desirable, the lookup should be
made conditional on a new CYGFUN_FS_ROM_FLASH_BLOCK_DEVICE_LOOKUP option which
"requires CYGPKG_IO_FLASH_BLOCK_DEVICE" to avoid forcing a dependency on
CYGPKG_IO_FLASH.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2010-11-11 14:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 11:19 [Bug 1001073] New: " bugzilla-daemon
2010-11-11 11:30 ` [Bug 1001073] " bugzilla-daemon
2010-11-11 14:53 ` bugzilla-daemon [this message]
2010-11-11 16:07 ` bugzilla-daemon
2010-11-13  9:29 ` bugzilla-daemon
2010-11-13 10:49 ` bugzilla-daemon
2010-11-24 18:43 ` bugzilla-daemon
2010-11-29 16:31 ` bugzilla-daemon
2010-11-30 10:35 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2010-11-11 11:19 [Bug 1001073] New: " bugzilla-daemon
2010-11-11 11:30 ` [Bug 1001073] " bugzilla-daemon
2010-11-11 14:53 ` bugzilla-daemon
2010-11-11 16:07 ` bugzilla-daemon
2010-11-13  9:29 ` bugzilla-daemon

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=20101111145258.47B211518842@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).