Hi
On 2015-06-08, Ander Conselvan De Oliveira wrote:
> On Mon, 2015-06-08 at 11:06 +0300, Ander Conselvan De Oliveira wrote:
> > On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
> > > On 2015-06-07, Ville Syrjälä wrote:
> > > > On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan
On Mon, 2015-06-08 at 11:06 +0300, Ander Conselvan De Oliveira wrote:
> On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-06-07, Ville Syrjälä wrote:
> > > On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > > > Hi
> > > >
> > > >
On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-06-07, Ville Syrjälä wrote:
> > On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > > Hi
> > >
> > > On 2015-04-20, Dave Airlie wrote:
> > > [...]
> > > > The following changes since
On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-06-07, Ville Syrjälä wrote:
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-04-20, Dave Airlie wrote:
[...]
The following changes since commit
Hi
On 2015-06-08, Ander Conselvan De Oliveira wrote:
On Mon, 2015-06-08 at 11:06 +0300, Ander Conselvan De Oliveira wrote:
On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
On 2015-06-07, Ville Syrjälä wrote:
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan
On Mon, 2015-06-08 at 11:06 +0300, Ander Conselvan De Oliveira wrote:
On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-06-07, Ville Syrjälä wrote:
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-04-20, Dave
Hi
On 2015-06-07, Ville Syrjälä wrote:
> On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-04-20, Dave Airlie wrote:
> > [...]
> > > The following changes since commit
> > > 09d51602cf84a1264946711dd4ea0dddbac599a1:
> > >
> > > Merge branch
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-04-20, Dave Airlie wrote:
> [...]
> > The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
> >
> > Merge branch 'turbostat' of
> >
> This commit introduces a regression relative to v4.0 on an Intel
> D945GCLF2 mainboard[1] (Atom 330) with Intel 82945G/GZ onboard graphics
> using its (only-) VGA connector for me.
>
Jani any ideas/plans?
Dave.
> v4.1-rc6-52-gff25ea8:
> [ 13.265699] BUG: unable to handle kernel NULL pointer
This commit introduces a regression relative to v4.0 on an Intel
D945GCLF2 mainboard[1] (Atom 330) with Intel 82945G/GZ onboard graphics
using its (only-) VGA connector for me.
Jani any ideas/plans?
Dave.
v4.1-rc6-52-gff25ea8:
[ 13.265699] BUG: unable to handle kernel NULL pointer
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-04-20, Dave Airlie wrote:
[...]
The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
Merge branch 'turbostat' of
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux
Hi
On 2015-06-07, Ville Syrjälä wrote:
On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
Hi
On 2015-04-20, Dave Airlie wrote:
[...]
The following changes since commit
09d51602cf84a1264946711dd4ea0dddbac599a1:
Merge branch 'turbostat' of
Hi
On 2015-04-20, Dave Airlie wrote:
[...]
> The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
>
> Merge branch 'turbostat' of
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux (2015-04-19 14:31:41
> -0700)
>
> are available in the git repository at:
>
>
Hi
On 2015-04-20, Dave Airlie wrote:
[...]
The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
Merge branch 'turbostat' of
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux (2015-04-19 14:31:41
-0700)
are available in the git repository at:
On Thu, Apr 23, 2015 at 5:30 PM, Bjorn Helgaas wrote:
> [+cc Matthew]
>
> On Tue, Apr 21, 2015 at 09:07:45AM -0700, Linus Torvalds wrote:
>> Hmm. The odd Intel PCI resource mess is back.
>>
>> Or maybe it never went away.
>>
>> I get these when suspending. Things *work*, but it's really spamming
On Thu, Apr 23, 2015 at 3:47 PM, Linus Torvalds
wrote:
> I'm not sure why we want that IORESOURCE_ROM_SHADOW thing at all, but
> yes, if what this is all about is the magic video ROM at 0xc, then
It's used in the PCI layer to say "Read from 0xc rather than the
ROM BAR" and then ends up
On Thu, Apr 23, 2015 at 2:56 PM, Matthew Garrett
wrote:
> On Thu, Apr 23, 2015 at 2:30 PM, Bjorn Helgaas wrote:
>>
>> int pcibios_add_device(struct pci_dev *dev)
>> {
>> if (dev-is-default-vga-device) {
>> dev->rom = 0xC;
>> dev->romlen = 0x2;
>> }
>
> I don't
On Thu, Apr 23, 2015 at 2:30 PM, Bjorn Helgaas wrote:
> Your i915 does not have a ROM BAR in hardware. If the default video
> device has no ROM BAR, pci_fixup_video() sets IORESOURCE_ROM_SHADOW
> even though the resource flags are zero because the BAR itself doesn't
> exist.
>
> If
[+cc Matthew]
On Tue, Apr 21, 2015 at 09:07:45AM -0700, Linus Torvalds wrote:
> Hmm. The odd Intel PCI resource mess is back.
>
> Or maybe it never went away.
>
> I get these when suspending. Things *work*, but it's really spamming
> my logs a fair bit:
>
> i915 :00:02.0: BAR 6: [???
[+cc Matthew]
On Tue, Apr 21, 2015 at 09:07:45AM -0700, Linus Torvalds wrote:
Hmm. The odd Intel PCI resource mess is back.
Or maybe it never went away.
I get these when suspending. Things *work*, but it's really spamming
my logs a fair bit:
i915 :00:02.0: BAR 6: [??? 0x
On Thu, Apr 23, 2015 at 2:30 PM, Bjorn Helgaas bhelg...@google.com wrote:
Your i915 does not have a ROM BAR in hardware. If the default video
device has no ROM BAR, pci_fixup_video() sets IORESOURCE_ROM_SHADOW
even though the resource flags are zero because the BAR itself doesn't
exist.
If
On Thu, Apr 23, 2015 at 2:56 PM, Matthew Garrett
matthew.garr...@coreos.com wrote:
On Thu, Apr 23, 2015 at 2:30 PM, Bjorn Helgaas bhelg...@google.com wrote:
int pcibios_add_device(struct pci_dev *dev)
{
if (dev-is-default-vga-device) {
dev-rom = 0xC;
dev-romlen =
On Thu, Apr 23, 2015 at 3:47 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
I'm not sure why we want that IORESOURCE_ROM_SHADOW thing at all, but
yes, if what this is all about is the magic video ROM at 0xc, then
It's used in the PCI layer to say Read from 0xc rather than the
On Thu, Apr 23, 2015 at 5:30 PM, Bjorn Helgaas bhelg...@google.com wrote:
[+cc Matthew]
On Tue, Apr 21, 2015 at 09:07:45AM -0700, Linus Torvalds wrote:
Hmm. The odd Intel PCI resource mess is back.
Or maybe it never went away.
I get these when suspending. Things *work*, but it's really
On Tue, Apr 21, 2015 at 11:07 AM, Linus Torvalds
wrote:
> Hmm. The odd Intel PCI resource mess is back.
>
> Or maybe it never went away.
>
> I get these when suspending. Things *work*, but it's really spamming
> my logs a fair bit:
>
> i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has
Hmm. The odd Intel PCI resource mess is back.
Or maybe it never went away.
I get these when suspending. Things *work*, but it's really spamming
my logs a fair bit:
i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
pci_bus :01: Allocating resources
pci_bus
Hmm. The odd Intel PCI resource mess is back.
Or maybe it never went away.
I get these when suspending. Things *work*, but it's really spamming
my logs a fair bit:
i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
pci_bus :01: Allocating resources
pci_bus
On Tue, Apr 21, 2015 at 11:07 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
Hmm. The odd Intel PCI resource mess is back.
Or maybe it never went away.
I get these when suspending. Things *work*, but it's really spamming
my logs a fair bit:
i915 :00:02.0: BAR 6: [???
Hi Linus,
First up, this tree contains a backmerge of your tree, as it merges cleanly
but then fails to build on ARM due to an API change, I've included the
fixed up patch in the merge commit.
The unmerged, unfixed tree is in my drm-next branch if you want to confirm
things. The fixup is 3
Hi Linus,
First up, this tree contains a backmerge of your tree, as it merges cleanly
but then fails to build on ARM due to an API change, I've included the
fixed up patch in the merge commit.
The unmerged, unfixed tree is in my drm-next branch if you want to confirm
things. The fixup is 3
30 matches
Mail list logo
