On Sat, 2007-10-06 at 08:59 -0700, Linus Torvalds wrote: > We do have a rule about "no regressions", so I think we'll have to do the > revert, but it would be nice to hear what the consequences for the revert > is for the affected hardware and new X.org.. No regressions is more important than making new X.org bits work. I'll make sure that any future fixes for this are tested against older X versions before having them sent along. -- keith.packard@intel.com
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: Revert "intel_agp: fix stolen mem range on G33"
- From: Jiri Slaby <jirislaby@gmail.com>
- Re: Revert "intel_agp: fix stolen mem range on G33"
- References:
- G33 graphics broken after 2.6.23-rc6
- From: Matthew Reppert <arashi@sacredchao.net>
- Re: G33 graphics broken after 2.6.23-rc6
- From: Kyle McMartin <kyle@mcmartin.ca>
- Re: G33 graphics broken after 2.6.23-rc6
- From: Kyle McMartin <kyle@mcmartin.ca>
- Revert "intel_agp: fix stolen mem range on G33"
- From: Kyle McMartin <kyle@mcmartin.ca>
- Re: Revert "intel_agp: fix stolen mem range on G33"
- From: Jiri Slaby <jirislaby@gmail.com>
- Re: Revert "intel_agp: fix stolen mem range on G33"
- From: Linus Torvalds <torvalds@linux-foundation.org>
- G33 graphics broken after 2.6.23-rc6
- Prev by Date: Re: [code] Unlimited partitions, a try
- Next by Date: Re: [PATCH] Cute feature: colored printk output
- Previous by thread: Re: Revert "intel_agp: fix stolen mem range on G33"
- Next by thread: Re: Revert "intel_agp: fix stolen mem range on G33"
- Index(es):
![]() |