From: Ben Elliston <bje@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Paul Miach <paul.miach@edion.com>, <sid@sources.redhat.com>
Subject: Re: best options for a wide bus?
Date: Fri, 05 Jan 2001 05:39:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.31.0101060038330.20243-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <20010105082219.B29055@redhat.com>
fche wrote:
The problem with extending the sid::bus class is that it impacts every
component. Using larger data types would imply adding support for
them into sidtypes.h, and we're already using the biggest standard one
(long long). This is not the easiest implementation avenue.
I think it would be a mistake to defer support for wider buses. If left
until later, the number of components that need to be upgraded will be much
larger.
Ben
next prev parent reply other threads:[~2001-01-05 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 20:10 Paul Miach
2001-01-04 20:20 ` Ben Elliston
2001-01-05 5:22 ` Frank Ch. Eigler
2001-01-05 5:39 ` Ben Elliston [this message]
2001-01-11 21:14 ` matthew green
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=Pine.LNX.4.31.0101060038330.20243-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=fche@redhat.com \
--cc=paul.miach@edion.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).