All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	David John <davidjon@xenontk.org>,
	Johan Hovold <jhovold@gmail.com>,
	linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] drm/kms: fix fbdev blanking regression
Date: Fri, 15 Jan 2010 13:10:47 +0000	[thread overview]
Message-ID: <20100115131047.41e7fa5e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1001151240030.2651@casper.infradead.org>

On Fri, 15 Jan 2010 12:40:30 +0000 (GMT)
James Simmons <jsimmons@infradead.org> wrote:

> 
> > > Yeap. I can have patch ready for you this weekend. I lack the hardware to
> > > test it tho. Never been able to find a intel pci card that is not built
> > > into the motherboard.
> > 
> > They don't exist, other than the old i740s.
> 
> I noticed the same is true for SiS cards.

SiS 6326 is a plug in card. Also prehistoric. I did a basic DRM for one
before deciding it would be faster to use the CPU (or indeed crayons ;))

  reply	other threads:[~2010-01-15 13:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 17:00 [bisected] drm/ksm: fbdev blanking regression in 2.6.33 Johan Hovold
2010-01-06 17:00 ` [PATCH] drm/kms: fix fbdev blanking regression Johan Hovold
2010-01-06 17:33   ` James Simmons
2010-01-06 18:09     ` Johan Hovold
2010-01-06 18:18       ` James Simmons
2010-01-06 19:12         ` Johan Hovold
2010-01-07  6:41           ` David John
2010-01-12 17:28             ` James Simmons
2010-01-12 17:34               ` Jesse Barnes
2010-01-13 19:48                 ` James Simmons
2010-01-13 20:01                   ` Alex Deucher
2010-01-15 12:40                     ` James Simmons
2010-01-15 13:10                       ` Alan Cox [this message]
2010-01-16 16:02                 ` James Simmons

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=20100115131047.41e7fa5e@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=davidjon@xenontk.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jhovold@gmail.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.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 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.