All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: David Miller <davem@davemloft.net>
Cc: airlied@gmail.com, mikpe@it.uu.se, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.26-rc1 broke X on SPARC Ultra5
Date: Wed, 04 Jun 2008 00:04:02 +0000	[thread overview]
Message-ID: <200806040204.03518.elendil@planet.nl> (raw)
In-Reply-To: <20080603.135449.193702216.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

David Miller wrote:
> Meanwhile X itself shipped mostly-non-working for PCI devices on sparc
> for years.  And would you also not argue that it's broken to begin
> with that the older X servers cannot work properly without a root PCI
> controller being there?

I can relate to that as starting X at one point ate the partition table on 
both my harddrives due to a PCI handling bug :-/
 
I assume this is not an issue with X.Org 7.3 (which is what Debian Lenny 
will probably release with)?

> I'm the only sparc64 platform developer, so my time is better spent
> moving forward and making sure that libpciaccess based X servers
> aren't so broken and do the right thing in a way which works in a
> maintainable long term manner.

From my limited perspective: agreed. And thanks for all the work you do.

Cheers,
FJP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Frans Pop <elendil@planet.nl>
To: David Miller <davem@davemloft.net>
Cc: airlied@gmail.com, mikpe@it.uu.se, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.26-rc1 broke X on SPARC Ultra5
Date: Wed, 4 Jun 2008 02:04:02 +0200	[thread overview]
Message-ID: <200806040204.03518.elendil@planet.nl> (raw)
In-Reply-To: <20080603.135449.193702216.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

David Miller wrote:
> Meanwhile X itself shipped mostly-non-working for PCI devices on sparc
> for years.  And would you also not argue that it's broken to begin
> with that the older X servers cannot work properly without a root PCI
> controller being there?

I can relate to that as starting X at one point ate the partition table on 
both my harddrives due to a PCI handling bug :-/
 
I assume this is not an issue with X.Org 7.3 (which is what Debian Lenny 
will probably release with)?

> I'm the only sparc64 platform developer, so my time is better spent
> moving forward and making sure that libpciaccess based X servers
> aren't so broken and do the right thing in a way which works in a
> maintainable long term manner.

From my limited perspective: agreed. And thanks for all the work you do.

Cheers,
FJP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-06-04  0:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  7:35 [BUG] 2.6.26-rc1 broke X on SPARC Ultra5 Mikael Pettersson
2008-06-03  7:35 ` Mikael Pettersson
2008-06-03 13:22 ` David Miller
2008-06-03 13:22   ` David Miller
2008-06-03 19:26   ` Mikael Pettersson
2008-06-03 19:26     ` Mikael Pettersson
2008-06-03 19:51     ` David Miller
2008-06-03 19:51       ` David Miller
     [not found]     ` <a5f334790806031259nc872dcekd00315d3e5bea048@mail.gmail.com>
2008-06-03 20:13       ` David Miller
2008-06-03 20:13         ` David Miller
2008-06-03 20:45     ` Dave Airlie
2008-06-03 20:45       ` Dave Airlie
2008-06-03 20:54       ` David Miller
2008-06-03 20:54         ` David Miller
2008-06-04  0:04         ` Frans Pop [this message]
2008-06-04  0:04           ` Frans Pop
2008-06-04  0:05           ` David Miller
2008-06-04  0:05             ` David Miller
2008-06-04  8:06         ` Mikael Pettersson
2008-06-04  8:06           ` Mikael Pettersson
2008-06-03 21:30 ` Dennis Gilmore
2008-06-03 21:30   ` Dennis Gilmore
2008-07-28 16:15 ` Daniel Smolik
2008-07-28 19:57 ` Friedrich Oslage

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=200806040204.03518.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=airlied@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=sparclinux@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.