Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Matthieu CRAPET <Matthieu.CRAPET@ingenico.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] files/device_table-minimal.txt: cleanup
Date: Fri, 04 Apr 2014 12:20:40 +0100	[thread overview]
Message-ID: <1396610440.13862.1.camel@ted> (raw)
In-Reply-To: <8672BB614B4CCA40A6B3BDD6FD82050B57551ADA@COSNADEXC13.usr.ingenico.loc>

On Thu, 2014-04-03 at 07:54 +0000, Matthieu CRAPET wrote:
> Hi Richard,
> 
> > If I remember correctly, mmc devices are dynamically allocated numbers.
> 
> Well, in my work experience, I always used this.
> However, according to include/uapi/linux/major.h:
> 
> #define MMC_BLOCK_MAJOR   179

I guess we should be ok then. I think the partition numbers can fail to
map but it would be rare that would happen and probably not at first
boot, or on the kind of environments the restricted dev directory would
be used in.

> > I only see ttyS, not S0 or S1?
> 
> According to file:
> /dev/ttyS	c	640	root	tty	4	64	0	1	2
> 
> This will create ttyS0 and ttyS1.

Sorry, yes, of course it will. I was getting confused...

Chewers,

Richard



      reply	other threads:[~2014-04-04 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 16:46 [RFC][PATCH] files/device_table-minimal.txt: cleanup Matthieu Crapet
2014-04-03  7:26 ` Richard Purdie
2014-04-03  7:54   ` Matthieu CRAPET
2014-04-04 11:20     ` Richard Purdie [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=1396610440.13862.1.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Matthieu.CRAPET@ingenico.com \
    --cc=openembedded-core@lists.openembedded.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