9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: [9front] [PATCH 0/3] improve igfx ironlake support
Date: Wed,  2 Mar 2022 02:26:35 -0800	[thread overview]
Message-ID: <20220302102638.14043-1-mforney@mforney.org> (raw)

Here are some patches I needed to get igfx working on my T410, which
has Ironlake graphics. It seems that Ironlake is very similar to
Sandy Bridge, but there are still a few differences, so it makes
sense to have its own TypeILK.

I have a few more patches for things I found in my debugging that
turned out to be red herrings, which I may send later, but let's
start with these.

Michael Forney (3):
  igfx: maintain single/double-channel LVDS mode from BIOS
  igfx: add TypeILK, since it differs slightly from SNB
  igfx: fix FDI link training on ironlake

 sys/src/cmd/aux/vga/igfx.c | 62 +++++++++++++++++++++++++++-----------
 1 file changed, 45 insertions(+), 17 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-03-02 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 10:26 Michael Forney [this message]
2022-03-02 10:26 ` [9front] [PATCH 1/3] igfx: maintain single/double-channel LVDS mode from BIOS Michael Forney
2022-03-02 10:26 ` [9front] [PATCH 2/3] igfx: add TypeILK, since it differs slightly from SNB Michael Forney
2022-03-02 10:26 ` [9front] [PATCH 3/3] igfx: fix FDI link training on ironlake Michael Forney
2022-03-02 18:33 ` [9front] [PATCH 0/3] improve igfx ironlake support cinap_lenrek
2022-03-02 19:01 ` cinap_lenrek

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=20220302102638.14043-1-mforney@mforney.org \
    --to=mforney@mforney.org \
    --cc=9front@9front.org \
    /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).