All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: unlisted-recipients:; (no To-header on input)
Cc: "Michel Dänzer" <michel@daenzer.net>,
	"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	Thomas@netline-mail2.netline.ch, "Dave Airlie" <airlied@linux.ie>,
	"Andrew Lutomirski" <luto@mit.edu>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jerome Glisse" <jglisse@redhat.com>,
	dri-devel@lists.sf.net, "Alex Deucher" <alexdeucher@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [git pull] drm: previous pull req + 1.
Date: Tue, 23 Jun 2009 09:28:12 -0700	[thread overview]
Message-ID: <20090623092812.16dffa97@jbarnes-g45> (raw)
In-Reply-To: <20090623083944.3e86ed2e@jbarnes-g45>

On Tue, 23 Jun 2009 08:39:44 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Tue, 23 Jun 2009 09:48:00 +0200
> Michel Dänzer <michel@daenzer.net> wrote:
> > On a side note, I did precisely that about ten years ago on my
> > Amiga. :) Granted, that was using two separate framebuffer devices
> > (X glint driver on top of pm2fb, debug messages on amifb), but I
> > think even that case isn't possible ATM. I agree it would be nice,
> > though realistically there's hardly a way around a second machine
> > for graphics driver development anyway.
> 
> Oh I know, most operating systems have reasonable debugging
> facilities, and have had for a long time.  Linux is the one lagging
> here.
> 
Heh, I saw "amiga" and stopped reading.  So it seems Linux on x86 is
the main laggard here...  I know PPC has had interesting debug features
for awhile now, and most arches have had kgdb for a long time.  Anyway,
there's plenty of work to do in this area to give Linux a decent system
level debugger...

--
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-06-23 16:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20  5:23 [git pull] drm: previous pull req + 1 Dave Airlie
2009-06-21  0:04 ` Maxim Levitsky
2009-06-21  0:42   ` Linus Torvalds
2009-06-21 14:47     ` Maxim Levitsky
2009-06-21 21:24       ` Chris Wilson
2009-06-22 18:09         ` Maxim Levitsky
2009-06-29  7:57           ` Chris Wilson
2009-06-30  9:49             ` Chris Wilson
2009-07-09 23:11             ` Eric Anholt
2009-06-21  1:33   ` Dave Airlie
2009-06-21  3:41 ` Andy Lutomirski
2009-06-21  5:16   ` Dave Airlie
2009-06-21 12:06     ` Andrew Lutomirski
2009-06-21 16:46     ` Linus Torvalds
2009-06-21 17:13       ` Linus Torvalds
2009-06-21 18:50         ` Andrew Lutomirski
2009-06-21 19:47           ` Linus Torvalds
2009-06-21 21:14             ` Andrew Lutomirski
2009-06-22  0:05               ` Andrew Lutomirski
2009-06-22 19:20                 ` Arnaldo Carvalho de Melo
2009-06-21 22:40             ` Dave Airlie
2009-06-22  8:18               ` Thomas Hellström
2009-06-22  8:30                 ` Dave Airlie
2009-06-22 18:22                 ` Linus Torvalds
2009-06-22 18:59                   ` Andrew Lutomirski
2009-06-22 19:43                     ` Linus Torvalds
2009-06-23  0:01                   ` Benjamin Herrenschmidt
2009-06-23  0:00                 ` Benjamin Herrenschmidt
2009-06-23  0:24                   ` Linus Torvalds
2009-06-23  1:04                     ` Benjamin Herrenschmidt
2009-06-23  1:18                       ` Jesse Barnes
2009-06-23  1:58                         ` Benjamin Herrenschmidt
2009-06-23  2:07                           ` Jesse Barnes
2009-06-23  2:26                             ` Benjamin Herrenschmidt
2009-06-23 15:40                               ` Jesse Barnes
2009-06-23  7:48                         ` Michel Dänzer
2009-06-23 15:39                           ` Jesse Barnes
2009-06-23 16:28                             ` Jesse Barnes [this message]
2009-06-22 23:57             ` Benjamin Herrenschmidt
2009-06-21 22:41       ` Dave Airlie

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=20090623092812.16dffa97@jbarnes-g45 \
    --to=jbarnes@virtuousgeek.org \
    --cc=Thomas@netline-mail2.netline.ch \
    --cc=airlied@linux.ie \
    --cc=alexdeucher@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=dri-devel@lists.sf.net \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=michel@daenzer.net \
    --cc=torvalds@linux-foundation.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.