[PATCH] YABEL support PCI accesses to other devices than the one yabel is running for

[Pattrick Hueper]

Hi,

Joseph and Stefan have had some fun using yabel on devices with
(intel?) onboard graphics cards. We found that those devices want to
read config space of other devices than the one yabel is running for.
This was previously impossible.

These patches introduce a yabel option
CONFIG_YABEL_ACCESS_OTHER_DEVICES that when set to 1/true allows
Option ROMs to find and access (read-only) other devices' config
space. Both through INT1A functions and cf8/cfc IO ports.

This allows the mentioned onboard graphics cards to be initialized by yabel.

The two 0001 patches add the corresponding Option to
Kconfig/Options.lb for v3/v2, the 0002 patch adds the functionality to
yabel.

Signed-off-by: Pattrick Hueper

Patty

[PATCH] YABEL support PCI accesses to other devices than the one yabel is running for

[Pattrick Hueper]

grr... too quick on the send button... here are the patch files...

Patty

On Wed, Mar 18, 2009 at 4:18 PM, Pattrick Hueper  wrote:
> Hi,
>
> Joseph and Stefan have had some fun using yabel on devices with
> (intel?) onboard graphics cards. We found that those devices want to
> read config space of other devices than the one yabel is running for.
> This was previously impossible.
>
> These patches introduce a yabel option
> CONFIG_YABEL_ACCESS_OTHER_DEVICES that when set to 1/true allows
> Option ROMs to find and access (read-only) other devices' config
> space. Both through INT1A functions and cf8/cfc IO ports.
>
> This allows the mentioned onboard graphics cards to be initialized by yabel.
>
> The two 0001 patches add the corresponding Option to
> Kconfig/Options.lb for v3/v2, the 0002 patch adds the functionality to
> yabel.
>
> Signed-off-by: Pattrick Hueper
>
> Patty

[PATCH] YABEL support PCI accesses to other devices than the one yabel is running for

[Joseph Smith]

On Wed, 18 Mar 2009 16:19:36 +0100, Pattrick Hueper 
wrote:
> grr... too quick on the send button... here are the patch files...
>
> Patty
>
> On Wed, Mar 18, 2009 at 4:18 PM, Pattrick Hueper 
> wrote:
> > Hi,
> >
> > Joseph and Stefan have had some fun using yabel on devices with
> > (intel?) onboard graphics cards. We found that those devices want to
> > read config space of other devices

Just to clarify Host Bridges
> > than the one yabel is running for.
> > This was previously impossible.
> >
> > These patches introduce a yabel option
> > CONFIG_YABEL_ACCESS_OTHER_DEVICES that when set to 1/true allows
> > Option ROMs to find and access (read-only) other devices' config
> > space. Both through INT1A functions and cf8/cfc IO ports.
> >
> > This allows the mentioned onboard graphics cards to be initialized by
>
> yabel.
> > The two 0001 patches add the corresponding Option to
> > Kconfig/Options.lb for v3/v2, the 0002 patch adds the functionality to
> > yabel.
> >
> > Signed-off-by: Pattrick Hueper

Tested and Acked-by: Joseph Smith

[PATCH] YABEL support PCI accesses to other devices than the one yabel is running for

[Pattrick Hueper]

On Wed, Mar 18, 2009 at 5:11 PM, Joseph Smith  wrote:
> Tested and Acked-by: Joseph Smith

Thanks, r4017 for v2 and r1154 and r1155 for v3

Pattrick