From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: i915 Skylake: "Invalid ROM contents"
Date: Wed, 18 Nov 2015 12:59:07 +0200 [thread overview]
Message-ID: <20151118105907.GC4437@intel.com> (raw)
In-Reply-To: <CALCETrXM5w0iCKDNBZYEpk17ViCMdP_B-cO4X01EQR9H8hesTw@mail.gmail.com>
On Tue, Nov 17, 2015 at 11:43:25AM -0800, Andy Lutomirski wrote:
> Typing:
>
> # cat /sys/devices/pci0000:00/0000:00:02.0/rom
>
> Provokes:
>
> i915 0000:00:02.0: Invalid ROM contents
Hmm. So there's no PCI option ROM there. I wonder what is there. I
get the same on my Braswell BTW. I tried to look through the UEFI
spec a bit, and it seems to say that even for non-legacy option ROMs
the 0x55aa signature should be there.
But this being the GPU means we may be using the shadow ROM stuff,
which IIRC assumes that the shadow is at 0xc000. I'm not sure that
holds anymore with UEFI, and maybe we should be using some UEFI
trick instead to find out where it actually lives?
BTW what does 'lspci -vv -s 00:02.0' say on your machine?
>
> This is on a Dell XPS 13 9350 (Skylake). This is 4.3.0 plus some
> wireless-next bits.
>
> --Andy
>
> --
> Andy Lutomirski
> AMA Capital Management, LLC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-18 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:43 i915 Skylake: "Invalid ROM contents" Andy Lutomirski
2015-11-18 10:59 ` Ville Syrjälä [this message]
2015-11-18 13:39 ` Alex Deucher
2015-11-18 15:59 ` [Intel-gfx] " Andy Lutomirski
2015-11-18 16:12 ` Daniel Stone
2016-01-10 18:41 ` Andy Lutomirski
2016-01-10 19:12 ` Andy Lutomirski
2016-02-29 16:31 ` Andy Lutomirski
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=20151118105907.GC4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luto@amacapital.net \
/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).