All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915/bios: do not discard address space
Date: Mon, 11 Nov 2019 13:10:10 +0200	[thread overview]
Message-ID: <87zhh24qjx.fsf@intel.com> (raw)
In-Reply-To: <20191108181852.f2ce7uthomzgf4vx@ldmartin-desk1>

On Fri, 08 Nov 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Nov 08, 2019 at 01:14:03PM +0200, Jani Nikula wrote:
>>Follow-up: store pointer to the oprom vbt somewhere under i915->vbt, and
>>have debugfs i915_vbt() handle that properly.
>
> I don't think this is needed. The thing I'm doing here is the same as
> what can be accomplished by reading the rom from sysfs:
>
> find /sys/bus/pci/devices/*/ -name rom
> ... choose one
>
> echo 1 > rom # to allow reading the rom
> hexdump -C rom

I think it'll eventually be needed because using debugfs i915_vbt is how
we tell people to dump the VBT for debugging, and that's what they're
accustomed to. (And yeah, we're missing that for pre-opregion machines.)

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/bios: do not discard address space
Date: Mon, 11 Nov 2019 13:10:10 +0200	[thread overview]
Message-ID: <87zhh24qjx.fsf@intel.com> (raw)
Message-ID: <20191111111010.yaR1lIY4du1BDzLMN2iNo08MTUyfl3itzVIJr6nYARg@z> (raw)
In-Reply-To: <20191108181852.f2ce7uthomzgf4vx@ldmartin-desk1>

On Fri, 08 Nov 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Nov 08, 2019 at 01:14:03PM +0200, Jani Nikula wrote:
>>Follow-up: store pointer to the oprom vbt somewhere under i915->vbt, and
>>have debugfs i915_vbt() handle that properly.
>
> I don't think this is needed. The thing I'm doing here is the same as
> what can be accomplished by reading the rom from sysfs:
>
> find /sys/bus/pci/devices/*/ -name rom
> ... choose one
>
> echo 1 > rom # to allow reading the rom
> hexdump -C rom

I think it'll eventually be needed because using debugfs i915_vbt is how
we tell people to dump the VBT for debugging, and that's what they're
accustomed to. (And yeah, we're missing that for pre-opregion machines.)

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-11-11 11:10 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  0:35 [PATCH 1/4] drm/i915/opregion: fix leaking fw on error path Lucas De Marchi
2019-11-08  0:35 ` [Intel-gfx] " Lucas De Marchi
2019-11-08  0:36 ` [PATCH 2/4] drm/i915/bios: rename bios to oprom when mapping pci rom Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:01   ` Jani Nikula
2019-11-08 10:01     ` [Intel-gfx] " Jani Nikula
2019-11-08  0:36 ` [PATCH 3/4] drm/i915/bios: make sure to check vbt size Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:08   ` Jani Nikula
2019-11-08 10:08     ` [Intel-gfx] " Jani Nikula
2019-11-08 17:41     ` Lucas De Marchi
2019-11-08 17:41       ` [Intel-gfx] " Lucas De Marchi
2019-11-08  0:36 ` [PATCH 4/4] drm/i915/bios: do not discard address space Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 11:14   ` Jani Nikula
2019-11-08 11:14     ` [Intel-gfx] " Jani Nikula
2019-11-08 18:18     ` Lucas De Marchi
2019-11-08 18:18       ` [Intel-gfx] " Lucas De Marchi
2019-11-08 19:19       ` Ville Syrjälä
2019-11-08 19:19         ` [Intel-gfx] " Ville Syrjälä
2019-11-08 20:14         ` Lucas De Marchi
2019-11-08 20:14           ` [Intel-gfx] " Lucas De Marchi
2019-11-08 21:02           ` Ville Syrjälä
2019-11-08 21:02             ` [Intel-gfx] " Ville Syrjälä
2019-11-08 21:09             ` Lucas De Marchi
2019-11-08 21:09               ` [Intel-gfx] " Lucas De Marchi
2019-11-11 11:10       ` Jani Nikula [this message]
2019-11-11 11:10         ` Jani Nikula
2019-11-10 16:57   ` kbuild test robot
2019-11-10 16:57     ` [Intel-gfx] " kbuild test robot
2019-11-10 16:57     ` kbuild test robot
2019-11-10 16:57   ` [RFC PATCH] drm/i915/bios: find_vbt() can be static kbuild test robot
2019-11-10 16:57     ` kbuild test robot
2019-11-10 16:57     ` [Intel-gfx] " kbuild test robot
2019-11-08  1:53 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/opregion: fix leaking fw on error path Patchwork
2019-11-08  1:53   ` [Intel-gfx] " Patchwork
2019-11-08  2:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-08  2:18   ` [Intel-gfx] " Patchwork
2019-11-08  9:16 ` [PATCH 1/4] " Jani Nikula
2019-11-08  9:16   ` [Intel-gfx] " Jani Nikula
2019-11-08 17:34   ` Lucas De Marchi
2019-11-08 17:34     ` [Intel-gfx] " Lucas De Marchi
2019-11-09 13:23 ` ✓ Fi.CI.IGT: success for series starting with [1/4] " Patchwork
2019-11-09 13:23   ` [Intel-gfx] " Patchwork

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=87zhh24qjx.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.