From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mike Travis <travis@sgi.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Mike Habeck <habeck@sgi.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Jacob Pan <jacob.jun.pan@intel.com>,
Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Yinghai <yinghai.lu@oracle.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Myron Stowe <myron.stowe@hp.com>
Subject: Re: [Patch 1/1] x86 pci: Add option to not assign BAR's if not already assigned
Date: Fri, 14 May 2010 17:00:04 -0700 [thread overview]
Message-ID: <20100514170004.6577415b@virtuousgeek.org> (raw)
In-Reply-To: <4BEDDF4F.3010902@zytor.com>
On Fri, 14 May 2010 16:39:59 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> On 05/14/2010 04:34 PM, Jesse Barnes wrote:
> >> I'm not lamenting that fact, because my experience is that what ends up
> >> replacing it is often far worse. Consider UARTs -- no MMU dependencies
> >> at all, can be accessed with four lines of assembly, and compare it to
> >> EHCI debug port, the driver for which is over 900 lines in the Linux
> >> kernel -- and that assumes that you're already in flat mode.
> >
> > Heh, you're so old and crufty!
>
> I know. Debugging is so 20th century.
Yeah, get with the times. Debugging on today's machines means you have
to look up register block offsets in ACPI, run some AML to setup your
debug port, and then load a microkernel onto the debug device to get
your vnc enabled debug console!
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-05-15 0:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 18:14 [Patch 1/1] x86 pci: Add option to not assign BAR's if not already assigned Mike Travis
2010-05-13 18:56 ` Bjorn Helgaas
2010-05-13 19:08 ` H. Peter Anvin
2010-05-13 19:12 ` Mike Travis
2010-05-13 19:13 ` Mike Travis
2010-05-13 19:54 ` Bjorn Helgaas
2010-05-13 20:27 ` Mike Habeck
2010-05-13 19:38 ` Mike Habeck
2010-05-13 20:02 ` Bjorn Helgaas
2010-05-13 20:09 ` H. Peter Anvin
2010-05-14 22:25 ` Jesse Barnes
2010-05-14 22:34 ` Mike Travis
2010-05-14 22:35 ` H. Peter Anvin
2010-05-14 22:40 ` Mike Travis
2010-05-15 2:25 ` Mike Travis
2010-05-14 22:47 ` Jesse Barnes
2010-05-14 22:59 ` Mike Travis
2010-05-14 23:06 ` Jesse Barnes
2010-05-14 23:23 ` Mike Travis
2010-05-14 23:33 ` Jesse Barnes
2010-05-14 23:40 ` H. Peter Anvin
2010-05-15 0:02 ` Jesse Barnes
2010-05-14 23:20 ` H. Peter Anvin
2010-05-14 23:28 ` Jesse Barnes
2010-05-14 23:32 ` H. Peter Anvin
2010-05-14 23:34 ` Jesse Barnes
2010-05-14 23:39 ` H. Peter Anvin
2010-05-15 0:00 ` Jesse Barnes [this message]
2010-05-15 0:14 ` H. Peter Anvin
2010-05-13 20:36 ` Yinghai Lu
2010-05-13 20:34 ` H. Peter Anvin
2010-05-13 18:58 ` Bjorn Helgaas
2010-05-28 16:53 ` Mike Travis
2010-05-28 17:00 ` H. Peter Anvin
2010-05-28 17:10 ` Mike Travis
2010-05-28 19:28 ` Jesse Barnes
2010-05-28 20:04 ` H. Peter Anvin
2010-05-31 11:12 ` Mike Travis
2010-05-31 16:36 ` H. Peter Anvin
2010-06-01 22:49 ` Bjorn Helgaas
2010-06-02 7:31 ` H. Peter Anvin
2010-06-02 15:45 ` Bjorn Helgaas
2010-06-02 15:47 ` H. Peter Anvin
2010-06-02 15:53 ` Jesse Barnes
2010-06-09 0:53 ` H. Peter Anvin
2010-06-09 1:26 ` Jesse Barnes
2010-06-09 14:23 ` Mike Habeck
2010-06-02 15:53 ` Mike Habeck
2010-06-02 16:40 ` Bjorn Helgaas
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=20100514170004.6577415b@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=bjorn.helgaas@hp.com \
--cc=habeck@sgi.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=myron.stowe@hp.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
--cc=yinghai.lu@oracle.com \
/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).