From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Re: amd64 and kernel configuration
Date: Wed, 27 Jul 2005 07:19:20 -0700 [thread overview]
Message-ID: <pan.2005.07.27.14.19.20.160692@cox.net> (raw)
In-Reply-To: 40bdd4fd0507270327575194a8@mail.gmail.com
Paolo Ripamonti posted <40bdd4fd0507270327575194a8@mail.gmail.com>,
excerpted below, on Wed, 27 Jul 2005 12:27:18 +0200:
> On 7/27/05, Duncan <1i5t5.duncan@cox.net> wrote:
>> I don't believe there's a
>> specific kernel option for it. (It's possible, however, that there is
>
> Spent my morning browsing make menuconfig, well... there is no voice
> regarding hypertransport so I guess you're right (unless it's time for me
> to take a sight exam :-P)
A likely more effective method of at least confirming whether there is
such a thing, if you don't already know where it is, would be to
view/pager/edit the .config file, since that puts it in flat format,
meaning you just have to go down the list, rather than browsing thru all
that nesting...
Of course, grepping for "hypertransport" (case insensitive) might be even
more useful, and quicker. Quickly opening a konsole to /usr/src/linux,
firing up mc, and doing a search on the term in question, yields a
surprising number of hits (this hypertransport in the kernel stuff is new
info to me as well). Hypertransport is as I mentioned an AMD connection
technology, but they've created a more or less open standard out of it,
and apparently, a decent enough number of MIPS and PPC hardware platforms
use it, that there is support in the Linux kernel on those platforms for
it. From the quick search I just did, it appears the kernel DOES have a
CONFIG_HYPERTRANSPORT option, but it only appears on MIPS, as a sub-option
dependent on the Yosemite chipset/platform/whatever-it-may-be. Apparently
on x86/x86_64/ppc hypertransport itself isn't an option, but something
that you either have or don't have, based on the characteristics of the
chipset drivers chosen.
Quite interesting, I must say. I had known AMD had opened the standard
and tried to make it a public one, but wasn't aware that some ppc and mips
platforms had incorporated it, so I'm learning something new in all this,
myself!
That's actually one of the reasons I so enjoy newsgroups and lists such as
this -- I never know when a question will come up that'll twist my
inquisitiveness of into areas I would have never explored on my own, and
I'll learn something either directly from the post content, or from my own
exploration stimulated by the content of the post. Those unexpected
"ah-ha!" moments, as the new idea clicks into place, filling an
information void I didn't know existed, are something I crave, in large
part /because/ they are sourced outside of myself, therefore something I
wouldn't ordinarily stumble across in my own semi-structured meanderings
in search of information.
So very cool, you guys stimulated me to learn something I would have
missed on my own, today! =8^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-27 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 6:29 [gentoo-amd64] amd64 and kernel configuration Dulmandakh Sukhbaatar
2005-07-27 6:10 ` [gentoo-amd64] " Duncan
2005-07-27 6:19 ` NY Kwok
2005-07-27 7:50 ` Dulmandakh Sukhbaatar
2005-07-27 7:04 ` Michal Žeravík
2005-07-27 9:58 ` netpython
2005-07-27 12:30 ` Brett Johnson
2005-07-27 15:58 ` [gentoo-amd64] " Duncan
2005-07-27 10:02 ` Duncan
2005-07-27 10:13 ` [gentoo-amd64] " Duncan
2005-07-27 10:27 ` Paolo Ripamonti
2005-07-27 14:19 ` Duncan [this message]
2005-07-27 14:31 ` [gentoo-amd64] " Paolo Ripamonti
2005-07-27 16:16 ` [gentoo-amd64] " Duncan
2005-07-27 10:46 ` [gentoo-amd64] " Drew Kirkpatrick
2005-07-27 15:42 ` [gentoo-amd64] " Duncan
2005-07-27 17:07 ` Jean.Borsenberger
2005-07-27 10:18 ` Duncan
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=pan.2005.07.27.14.19.20.160692@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.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