From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ulrich Teichert <krypton@ulrich-teichert.org>
Cc: Michael Cree <mcree@orcon.net.nz>,
Guenter Roeck <linux@roeck-us.net>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
Helge Deller <deller@gmx.de>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
alpha <linux-alpha@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org, Netdev <netdev@vger.kernel.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Introduce and use absolute_pointer macro
Date: Sat, 18 Sep 2021 10:04:20 -0700 [thread overview]
Message-ID: <CAHk-=whY5mLggPSr2U00mqgUbRJYnYSxtNZm4FnEtQrHftYr8Q@mail.gmail.com> (raw)
In-Reply-To: <202109181311.18IDBKQB005215@valdese.nms.ulrich-teichert.org>
On Sat, Sep 18, 2021 at 6:11 AM Ulrich Teichert
<krypton@ulrich-teichert.org> wrote:
>
> Hi,
>
> >
> > On Thu, Sep 16, 2021 at 11:35:36AM -0700, Linus Torvalds wrote:
> > > Naah. I think the Jensen actually had an ISA slot. Came with a
> > > whopping 8MB too, so the ISA DMA should work just fine.
> > >
> > > Or maybe it was EISA only? I really don't remember.
>
> It's EISA only. I've made some pictures of a somewhat dusty inside of
> a Jensen with 4 EISA cards (from bottom to top: SCSI, video, 2x network):
Ok.
Looking around the config options, there _are_ systems with ISA slots,
but it's not the old Jensen one. It's apparently some evaluation
boards but also the "AlphaPC64" one.
So we do want CONFIG_ISA for alpha, even if not Jensen.
(I forget which alpha I had. For some reason I want to think I had an
EISA machine and probably Jensen. Maybe upgraded to a 164 later?)
> I could not get a recent kernel to boot, but it's booting ancient kernels
> just fine:
>
> Linux version 2.4.27-2-generic (tretkowski@bastille) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Sun May 29 18:40:58 UTC 2005
Ouch. Without having some kind of bisection, I guess we'll never know.
And I assume it's not really been tested since, so it could be
multiple reasons, including compiler updates causing dodgy code to not
work etc etc.
> While we're at it, during my vain attempts to get new kernels to boot,
> I tried to disable PCI support to make the kernels smaller (after all,
> the Jensen has only EISA, so what good would PCI support for?) and
> got it to compile with the attached patch (which fixes some warnings,
> too).
Can you send me your Jensen config?
I do not see why you should be using that horrible __EXERN_INLINE. It
will cause gcc to sometimes not inline at all, and not generate the
out-of-line body either.
Sometimes that is what you want: you want to generate one single body
of the function, and particularly one that is _different_ from the
inlining case (ie for inlining you want to do the simple thing, for
out-of-line you do something fancier).
But that isn't the case here, so this looks like a workaround for
something else. But this code does end up using preprocessor
concatenation etc, so I might be missing some case.
Linus
next prev parent reply other threads:[~2021-09-18 17:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 3:52 [PATCH v2 0/4] Introduce and use absolute_pointer macro Guenter Roeck
2021-09-15 3:52 ` [PATCH v2 1/4] compiler.h: Introduce " Guenter Roeck
2021-09-15 7:07 ` Geert Uytterhoeven
2021-09-15 7:13 ` Geert Uytterhoeven
2021-09-15 14:03 ` Guenter Roeck
2021-09-15 3:52 ` [PATCH v2 2/4] net: i825xx: Use absolute_pointer for memcpy from fixed memory location Guenter Roeck
2021-09-15 7:08 ` Geert Uytterhoeven
2021-09-15 3:52 ` [PATCH v2 3/4] alpha: Move setup.h out of uapi Guenter Roeck
2021-09-15 3:52 ` [PATCH v2 4/4] alpha: Use absolute_pointer to define COMMAND_LINE Guenter Roeck
2021-09-15 19:18 ` [PATCH v2 0/4] Introduce and use absolute_pointer macro Linus Torvalds
2021-09-15 19:35 ` Guenter Roeck
2021-09-15 19:47 ` Linus Torvalds
2021-09-15 19:50 ` Linus Torvalds
2021-09-15 21:19 ` Linus Torvalds
2021-09-16 7:02 ` Anders Larsen
2021-09-16 16:25 ` Linus Torvalds
2021-09-15 20:30 ` Helge Deller
2021-09-15 22:33 ` Guenter Roeck
2021-09-16 18:35 ` Linus Torvalds
2021-09-18 9:51 ` Michael Cree
2021-09-18 13:11 ` Ulrich Teichert
2021-09-18 17:04 ` Linus Torvalds [this message]
2021-09-18 17:17 ` Thorsten Glaser
2021-09-18 17:21 ` Linus Torvalds
2021-09-18 17:28 ` Linus Torvalds
2021-09-18 20:26 ` Ulrich Teichert
2021-09-18 20:46 ` Linus Torvalds
2021-09-18 21:12 ` Linus Torvalds
2021-09-18 22:09 ` Linus Torvalds
2021-09-19 15:13 ` Dave Taht
2021-09-20 18:25 ` Ulrich Teichert
2021-09-20 18:46 ` Linus Torvalds
2021-09-20 18:59 ` Matt Turner
2021-09-20 19:45 ` Linus Torvalds
2021-09-21 19:13 ` Ulrich Teichert
2021-09-21 20:42 ` Linus Torvalds
2021-09-21 21:39 ` Linus Torvalds
2021-09-22 20:50 ` Ulrich Teichert
2021-09-16 19:47 ` Linus Torvalds
2021-09-16 0:34 ` Michael Cree
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='CAHk-=whY5mLggPSr2U00mqgUbRJYnYSxtNZm4FnEtQrHftYr8Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=krypton@ulrich-teichert.org \
--cc=kuba@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=netdev@vger.kernel.org \
--cc=rth@twiddle.net \
/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 NNTP newsgroup(s).