From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
"Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
pjones@redhat.com
Subject: Re: Re-add ibft tree to linux-next please
Date: Mon, 12 Dec 2011 21:15:37 -0500 [thread overview]
Message-ID: <20111213021536.GC2730@konrad-lan> (raw)
In-Reply-To: <4EE68D57.7030603@zytor.com>
On Mon, Dec 12, 2011 at 03:25:11PM -0800, H. Peter Anvin wrote:
> On 12/12/2011 06:53 AM, Konrad Rzeszutek Wilk wrote:
> > Hey Stephen,
> >
> > I've one patch for the iBFT and since I am the co-maintainer of said tree,
> > please add this tree to your awesome build system:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft.git
> >
> > The branch is "linux-next"
> >
> > Signed-off-by: Konrad Rzeszutek Wilk <konrad@kernel.org>
> > CC: Peter Jones <pjones@redhat.com>
> > Thanks!
> >
> > P.S.
> > After kernel.org went down, I choose not to resurface the iBFT tree b/c I
> > figured that the driver was sooo stable that there would be no need for any
> > patches. Well, not the case
>
> iBFT is basically an ACPI table with nonstandard discovery. Any way we
> could get this merged into the ACPI core eventually?
Part of the driver has been exported to the SCSI tree already (the software and
broadcam iSCSI one). The only two remainig pieces are the SysFS skeleton
(which should probably still sit in drivers/firmware) and iBFT finder.
The remaining piece that could be moved to drivers/acpi is the "finder" of
the IBFT which can find it via ACPI, similar to how MADT tables are found
(so perhaps arch/x86/acpi?).
The trick is that we also have to retain the code functionality if
"# CONFIG_ACPI is not set" to scan the memory for the iBFT. That part
should definitly _not_ be moved to drivers/acpi. It could be moved to
arch/x86/ .. but it could also stay in drivers/firmware. <shrugs>
next prev parent reply other threads:[~2011-12-13 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:53 Re-add ibft tree to linux-next please Konrad Rzeszutek Wilk
2011-12-12 22:44 ` Stephen Rothwell
2011-12-12 23:10 ` Konrad Rzeszutek Wilk
2011-12-12 23:25 ` H. Peter Anvin
2011-12-13 2:15 ` Konrad Rzeszutek Wilk [this message]
2012-01-17 14:08 ` Len Brown
2012-01-17 16:49 ` Konrad Rzeszutek Wilk
2012-01-17 17:37 ` H. Peter Anvin
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=20111213021536.GC2730@konrad-lan \
--to=konrad@darnok.org \
--cc=hpa@zytor.com \
--cc=konrad@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).