mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, x86@kernel.org, giancarlo.asnaghi@st.com
Subject: Re: x86/Kconfig: where to place a new chipset
Date: Thu, 27 Oct 2011 07:54:30 +0200	[thread overview]
Message-ID: <4EA8F216.30807@zytor.com> (raw)
In-Reply-To: <20111027011737.GA17910@mail.gnudd.com>

On 10/27/2011 03:17 AM, Alessandro Rubini wrote:
> Hello.
> 
> I'm currently working on a PCIe chipset (or IO-Hub), called STA2X11.
> The device hosts a number of peripherals (sata, ether, spi, uart, ...)
> and a DMA controller.  The individual PCI functions can't be enabled
> by themselves, as chip support must be activated first.  This is both
> because some internal mappings must be setup and because internal
> device functions rely on the internal DMA engine. Actually, an
> instance of swiotlb is being used.
> 
> While I'm sure core code should be in arch/x86/platform (and there is
> where I placed the initialization code), I'm wondering where should
> the device fall in the Kconfig tree. I tend to put it in the
> X86_32_NON_STANDARD stanza, even if the resulting kernel will also
> work on standard computers (the "SGI Visual Workstation" config option
> does the same).
> 
> On the other hand, the device can either be the core chipset (main use
> case) or it can be plugged on a PCIe board.
> 

The nonstandard platform location seems fine to me.

	-hpa


      reply	other threads:[~2011-10-27  5:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  1:17 Alessandro Rubini
2011-10-27  5:54 ` H. Peter Anvin [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=4EA8F216.30807@zytor.com \
    --to=hpa@zytor.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rubini@gnudd.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

Powered by JetHome