From: Ed Vance <EdV@macrolink.com>
To: "'Russell King'" <rmk@arm.linux.org.uk>
Cc: "'Bill Nottingham'" <notting@redhat.com>,
"'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 kudzu - discussion
Date: Fri, 8 Mar 2002 10:12:30 -0800 [thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D13A76E6@EXCHANGE> (raw)
On Fri Mar 08, 2002, Russell King wrote:
>
> I think there are two bugs here that need treating in different ways.
>
> 1. Not displaying port statistics for iomem-based ports. This is
> probably an oversight when iomem ports were added to the serial
> driver.
>
> 2. "port:" entry being 0. I don't think we really want to report IO
> port or memory addresses here without giving userspace some
> indication which we're reporting.
>
> For 2, I'd suggest replacing "port:" with "mem:" for iomem ports, and
> changing the serinfo: line to reflect the changed format (this is
> probably ignored by kudzu though.)
>
> Does this sound reasonable?
Hi Russell,
Yes. I'll change the serinfo line rev marking from 1.0 to 1.1 and label
the iomem value as "mem". If I remember correctly, kudzu detects that
field by its delimiters, so it does not matter that we change the field
label. It's probably easiest for me to verify by just trying it. If there
is a surprise there, I will inform Bill Nottingham at Red Hat.
Also, I'll verify that the port statistics flow unit runs for the iomem
case.
Thanks,
Ed Vance
next reply other threads:[~2002-03-08 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 18:12 Ed Vance [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 0:34 Ed Vance
2002-03-08 19:15 Ed Vance
2002-03-07 23:12 Ed Vance
2002-03-08 9:49 ` Russell King
2002-03-08 10:25 ` David Woodhouse
2002-03-07 22:23 Ed Vance
2002-03-07 22:34 ` Bill Nottingham
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=11E89240C407D311958800A0C9ACF7D13A76E6@EXCHANGE \
--to=edv@macrolink.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=notting@redhat.com \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®