From: Russell King <rmk@arm.linux.org.uk>
To: Ed Vance <EdV@macrolink.com>
Cc: "'linux-serial'" <linux-serial@vger.kernel.org>,
"'linux-kernel'" <linux-kernel@vger.kernel.org>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] serial.c procfs 2nd try - discussion
Date: Tue, 12 Mar 2002 09:11:44 +0000 [thread overview]
Message-ID: <20020312091144.A11914@flint.arm.linux.org.uk> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76EF@EXCHANGE>
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76EF@EXCHANGE>; from EdV@macrolink.com on Mon, Mar 11, 2002 at 05:41:09PM -0800
On Mon, Mar 11, 2002 at 05:41:09PM -0800, Ed Vance wrote:
> 2. Does anybody know of anything that will break because of the leading
> zeros that are now present on the address field?
I'm not overly happy with this idea - there isn't anything that says an
ioport address has 4 digits. I know of machines where an ioport address
has 8, and I'm sure on the Alpha or Sparc64 its probably 16 digits.
It might be a better solution to leave the 'port:' element as-is if
programs like kudzu rely on that label there, and just fix the missing
statistics for iomem ports.
Then file a bug against kudzu and get them to fix that so it doesn't
SEGV when it finds something it doesn't like, and teach it about the
'mem' tag.
If kudzu ignores the serinfo: line as well, that's also another kudzu
bug.
Then fix the proc interface to report a 'mem' tag for each port.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-03-12 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:41 [PATCH] serial.c procfs 2nd try - discussion Ed Vance
2002-03-12 9:11 ` Russell King [this message]
2002-03-12 9:27 ` Jeff Garzik
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=20020312091144.A11914@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=EdV@macrolink.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox