All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Eric Nelson <eric.nelson@boundarydevices.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm-extra][PATCH] linux-boundary: enable some PCIe drivers
Date: Wed, 15 May 2013 16:48:21 +0200	[thread overview]
Message-ID: <20130515164821.694ba1ff@e6520eb> (raw)
In-Reply-To: <519398A5.9050501@boundarydevices.com>

Hi Eric,

Le Wed, 15 May 2013 07:16:05 -0700,
Eric Nelson <eric.nelson@boundarydevices.com> a écrit :
> That said, I'm not really sure where Eric's headed by including somewhat
> arbitrary PCIe devices. I'm not aware that these are commonly used and
> could begin a slow march to allyesconfig. Do other users really want
> to include support for PCIe 8250's, or is this just something important
> for a project of yours?
> 
that was just the result of tests I did on PCIe with standard
peripherals I bought in a computer shop to test PCIe with several
different kind of peripgerals.

This patch simply gives a chance to users to have their PCIe board
working (of course if that's one of those which I tested and  there
are other PCIe drivers not enabled).

Forget this patch if you believe that's not a good idea, I really
don't care if it's not applied ;-)

Eric


  reply	other threads:[~2013-05-15 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 14:02 [meta-fsl-arm-extra][PATCH] linux-boundary: enable some PCIe drivers Eric Bénard
2013-05-14 14:08 ` Fabio Estevam
2013-05-14 14:20   ` Eric Bénard
2013-05-14 20:22     ` Otavio Salvador
2013-05-15  7:51       ` Eric Bénard
2013-05-15 11:48         ` Otavio Salvador
2013-05-15 14:16         ` Eric Nelson
2013-05-15 14:48           ` Eric Bénard [this message]
2013-05-15 16:55             ` Eric Nelson
2013-05-15 17:08               ` Otavio Salvador

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=20130515164821.694ba1ff@e6520eb \
    --to=eric@eukrea.com \
    --cc=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.