From: "David S. Miller" <davem@redhat.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: milang@tal.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, greg@kroah.com
Subject: Re: Linux 2.4.23-rc1
Date: Tue, 11 Nov 2003 15:08:15 -0800 [thread overview]
Message-ID: <20031111150815.6a8aff01.davem@redhat.com> (raw)
In-Reply-To: <20031111231027.GC24159@parcelfarce.linux.theplanet.co.uk>
On Tue, 11 Nov 2003 23:10:27 +0000
viro@parcelfarce.linux.theplanet.co.uk wrote:
> > ir-usb.c should not assume all baud speed rate macros are
> > available on all platforms.
>
> Umm... Why are they defined in asm-*/* and not in linux/*?
Because each platform may wish to use different values
for these things as they are part of the user visible ABI.
For example, on Sparc we choose values which matched up closely
to what SunOS uses in order to make the compatability layer
for SunOS binaries easier to implement.
It just so happens that the bits are layed out on Sparc such
that we could only fit so many baud rate encodings, we didn't
have enough left to define one for B4000000.
You will notice that in the entire 2.6.x tree, ir-usb.c is the
only piece of code which makes reference to this value.
next prev parent reply other threads:[~2003-11-11 23:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 19:28 Linux 2.4.23-rc1 Marcelo Tosatti
2003-11-11 0:20 ` J.A. Magallon
2003-11-11 15:09 ` Willy Tarreau
2003-11-11 21:27 ` Kaj-Michael Lang
2003-11-11 22:18 ` Kaj-Michael Lang
2003-11-11 22:57 ` David S. Miller
2003-11-11 23:10 ` viro
2003-11-11 23:08 ` David S. Miller [this message]
2003-11-12 1:54 ` Greg KH
2003-11-12 6:36 ` David S. Miller
2004-01-05 22:39 ` Greg KH
2003-11-12 6:19 ` Willy Tarreau
2003-11-12 6:49 ` glee
2003-11-12 8:59 ` Dave Jones
2003-11-12 9:10 ` Willy Tarreau
2003-11-12 9:30 ` glee
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=20031111150815.6a8aff01.davem@redhat.com \
--to=davem@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=milang@tal.org \
--cc=sparclinux@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.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