Re-add ibft tree to linux-next please

Re-add ibft tree to linux-next please

[Konrad Rzeszutek Wilk]

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

Re: Re-add ibft tree to linux-next please

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]

Hi Konrad,

On Mon, 12 Dec 2011 10:53:30 -0400 Konrad Rzeszutek Wilk <konrad@kernel.org> wrote:
>
> 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"

OK, I have added that from today.  There is currently nothing in that
branch, right?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Re-add ibft tree to linux-next please

[Konrad Rzeszutek Wilk]

On Tue, Dec 13, 2011 at 09:44:19AM +1100, Stephen Rothwell wrote:
> Hi Konrad,
> 
> On Mon, 12 Dec 2011 10:53:30 -0400 Konrad Rzeszutek Wilk <konrad@kernel.org> wrote:
> >
> > 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"
> 
> OK, I have added that from today.  There is currently nothing in that
> branch, right?

Yup. I want to shakedown the patches first in my #testing on first so that
you aren't hit with any compile errors.

> 
> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgment of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window. 
> 
> You will need to ensure that the patches/commits in your tree/series have
> been:
>      * submitted under GPL v2 (or later) and include the Contributor's
> 	Signed-off-by,
>      * posted to the relevant mailing list,
>      * reviewed by you (or another maintainer of your subsystem tree),
>      * successfully unit tested, and 
>      * destined for the current or next Linux merge window.
> 
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.
> 
> -- 
> Cheers,
> Stephen Rothwell 
> sfr@canb.auug.org.au
> 
> Legal Stuff:
> By participating in linux-next, your subsystem tree contributions are
> public and will be included in the linux-next trees.  You may be sent
> e-mail messages indicating errors or other issues when the
> patches/commits from your subsystem tree are merged and tested in
> linux-next.  These messages may also be cross-posted to the linux-next
> mailing list, the linux-kernel mailing list, etc.  The linux-next tree
> project and IBM (my employer) make no warranties regarding the linux-next
> project, the testing procedures, the results, the e-mails, etc.  If you
> don't agree to these ground rules, let me know and I'll remove your tree
> from participation in linux-next.

Re: Re-add ibft tree to linux-next please

[H. Peter Anvin]

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?

	-hpa

Re: Re-add ibft tree to linux-next please

[Konrad Rzeszutek Wilk]

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>

Re: Re-add ibft tree to linux-next please

[Len Brown]

> 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>


Are there really hardware/firmware configurations that support IBFT
and do not support ACPI?

If yes, do they require an OS that has CONFIG_ACPI=n?
Or would finding the table with CONFIG_ACPI=y and acpi_disabled=1
be sufficient?

-Len

Re: Re-add ibft tree to linux-next please

[Konrad Rzeszutek Wilk]

On Tue, Jan 17, 2012 at 09:08:30AM -0500, Len Brown wrote:
> 
> > 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>
> 
> 
> Are there really hardware/firmware configurations that support IBFT
> and do not support ACPI?

gPXE can be used in legacy environments. And it (gPXE) does not update
the ACPI tables.

> 
> If yes, do they require an OS that has CONFIG_ACPI=n?

I can't think of anybody nowadays doing CONFIG_ACPI=n for x86.
Is there anybody doing it?


> Or would finding the table with CONFIG_ACPI=y and acpi_disabled=1
> be sufficient?

I think that would work. And also if 'acpi_disabled=0' as you might
have an IBFT table in memory that is _not_ hooked up to the ACPI tables.

Re: Re-add ibft tree to linux-next please

[H. Peter Anvin]

On 01/17/2012 08:49 AM, Konrad Rzeszutek Wilk wrote:
>>
>> Are there really hardware/firmware configurations that support IBFT
>> and do not support ACPI?
> 
> gPXE can be used in legacy environments. And it (gPXE) does not update
> the ACPI tables.
> 

That's irrelevant.  THe point is that iBFT *is* an ACPI table.

> I think that would work. And also if 'acpi_disabled=0' as you might
> have an IBFT table in memory that is _not_ hooked up to the ACPI tables.

That is *always* the case, the "finder" is nonstandard (because the ACPI
tables are largely non-extensible, says the one who has tried to
actually extend ACPI tables in memory.)

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.