From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Woody Wu <narkewoody@gmail.com>
Cc: kernelnewbies@kernelnewbies.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: What does ISA/PCI really mean to ARM architecture?
Date: Thu, 27 Dec 2012 10:51:40 +0100 [thread overview]
Message-ID: <CAMuHMdWbyrDaaV5TWiEafEpjuscoGKXKKYzNBw_CSSWYLbNaPQ@mail.gmail.com> (raw)
In-Reply-To: <20121227082724.GA11775@zuhnb712.ap.bm.net>
On Thu, Dec 27, 2012 at 9:27 AM, Woody Wu <narkewoody@gmail.com> wrote:
> Can a peripheral chip that claims to be ISA or PCI device be used in a
> ARM based embedded system? For these kind of chips, I only concern
> about the planar kind of devices, means they are not on a dedicated
> expansion card.
>
> From hardware point of view, to attach a ISA or PCI planar chip, is
> there any requirement need to fulfill on a ARM bard?
>
> From Linux driver point of view, what are needed to support an ISA or
> PCI driver in ARM architecture? More important, is ISA or PCI device a
> platform device? If not, how to add these kind of devices in my board
> definition?
An ISA device is typically a platform device. For ARM, which uses device trees,
this means you define it in the device tree.
A PCI device is not a platform device, as devices on a PCI bus can be
probed automatically. The PCI host bridge is typically a platform device,
though, so it it should be in your device tree.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2012-12-27 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 8:27 Woody Wu
2012-12-27 9:51 ` Geert Uytterhoeven [this message]
2012-12-27 14:19 ` anish kumar
2012-12-27 16:07 ` Arnd Bergmann
2012-12-27 16:22 ` jonsmirl
2012-12-27 16:46 ` anish kumar
2012-12-27 17:10 ` jonsmirl
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=CAMuHMdWbyrDaaV5TWiEafEpjuscoGKXKKYzNBw_CSSWYLbNaPQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narkewoody@gmail.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
all inboxes | Powered by JetHome®