From: "Eric DEJONC" <eric.dejonc@thales-e-transactions.com>
To: Jeremy Bowen <Jeremy.Bowen@opennw.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: mtd devices
Date: Wed, 16 Apr 2003 09:19:56 +0200 [thread overview]
Message-ID: <3E9D041C.C5BEAD3C@thales-e-transactions.com> (raw)
In-Reply-To: DEA23DB61B62D4118B5900508B323B8401055531@OPENMAIL
Hi,
It doesn't change anything if you chose one format than the other. Special
files can be placed where you want and can have the name you want. The only
thing there is in the file is the major and minor num and a boolean that
indicates if it is a char device or a block device.
regards,
Eric
Jeremy Bowen a écrit :
> Hi
>
> I've seen various references to both
> 1) "/dev/mtd/x" and
> 2) "/dev/mtdx".
>
> My system uses the 1st format. Could someone please help me understand the
> differences between these two formats and where they come from.
>
> Thanks
>
> Jeremy
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2003-04-16 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:57 mtd devices Jeremy Bowen
2003-04-16 7:19 ` Eric DEJONC [this message]
2003-04-16 9:52 ` Daniel Toussaint
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=3E9D041C.C5BEAD3C@thales-e-transactions.com \
--to=eric.dejonc@thales-e-transactions.com \
--cc=Jeremy.Bowen@opennw.com \
--cc=linux-mtd@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