From: Ulrich Teichert <krypton@ulrich-teichert.org>
To: torvalds@linux-foundation.org (Linus Torvalds)
Cc: krypton@ulrich-teichert.org (Ulrich Teichert),
mcree@orcon.net.nz (Michael Cree),
linux@roeck-us.net (Guenter Roeck),
rth@twiddle.net (Richard Henderson),
ink@jurassic.park.msu.ru (Ivan Kokshaysky),
mattst88@gmail.com (Matt Turner),
James.Bottomley@hansenpartnership.com (James E . J . Bottomley),
deller@gmx.de (Helge Deller),
davem@davemloft.net (David S . Miller),
kuba@kernel.org (Jakub Kicinski),
linux-alpha@vger.kernel.org (alpha),
geert@linux-m68k.org (Geert Uytterhoeven),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
linux-parisc@vger.kernel.org, netdev@vger.kernel.org (Netdev),
linux-sparse@vger.kernel.org (Sparse Mailing-list)
Subject: Re: [PATCH v2 0/4] Introduce and use absolute_pointer macro
Date: Mon, 20 Sep 2021 20:25:54 +0200 (CEST) [thread overview]
Message-ID: <202109201825.18KIPsV4026066@valdese.nms.ulrich-teichert.org> (raw)
In-Reply-To: <CAHk-=wh-=tMO9iCA4v+WgPSd+Gbowe5kptwo+okahihnO2fAOA@mail.gmail.com>
Hi,
[sorry for the late answer, I was sick yesterday with digestive
system trouble, but nothing serious, just painful....]
> On Sat, Sep 18, 2021 at 1:26 PM Ulrich Teichert
> <krypton@ulrich-teichert.org> wrote:
> >
> > I was just tinkering with it to get it compiled without warning,
> > I certainly didn't get the big picture :-/
>
> Ok, you shamed me into some tinkering too, and I fixed a couple of
> issues with the alpha build.
>
> The whole "pci_iounmap()" mess is not something I solved (you were
> cc'd on the email I sent out about that), but I did test a few
> different Jensen configurations and fixed a couple of uglies.
>
> So at least _some_ Jensen configurations build cleanly once more, and
> I re-enabled JENSEN as a valid machine target.
Yes, I was able to build a minimal Jensen config without any warning
after pulling today, thanks! I think investing a bit in cleaning up
non-PCI configurations may help as soon as PCIe will be obsoleted
by the next bus system ;-)
> But if it doesn't boot, it's all fairly moot. And those things are a
> pain to debug, and if the last booting kernel was years and years ago,
> I don't think it realistically will necessarily ever be fixed.
The main trouble is that my system has only 64MB of memory and the smallest
kernel image with all drivers I need was about 105MB big. According
to: http://users.bart.nl/~geerten/FAQ-9.html
the Jensen can take up to 128MB of RAM and the required PS/2 SIMMs
with partity are still available on ebay, so I just bought 4x32 MB SIMMs.
After setting CONFIG_CC_OPTIMIZE_FOR_SIZE the kernel image was still
93MB big, but with 128MB I should be able to boot it. Let's see....
> Oh well. I have an odd love-hate relationship with alpha.
>
> I think it's one of the worst architectures ever designed (memory
> ordering is completely broken, and the lack of byte operations in the
> original specs were a big reason for the initial problems and eventual
> failure).
I didn't had the money for an Alpha at that time, but as soon as
cheap systems were available on ebay, I took the opportunity. At the
time I bought them, I considered the Miatas (the "Personal Workstations"
from DEC) as quite fast - that must have been around 2004/2006.
> But at the same time, I really did enjoy it back in the day, and it
> _was_ the first port I did, and the first truly integrated kernel
> architecture (the original Linux m68k port that preceded it was a
> "hack up and replace" job rather than "integrate")
My experience is that each port is good for code quality, but I can
only state that for user space applications, not having done much kernel
work,
CU,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de | Listening to:
Stormweg 24 |Eat Lipstick: Dirty Little Secret, The Baboon Show:
24539 Neumuenster, Germany|Work Work Work, The Bellrays: Bad Reaction
next prev parent reply other threads:[~2021-09-21 2:48 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
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 [this message]
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=202109201825.18KIPsV4026066@valdese.nms.ulrich-teichert.org \
--to=krypton@ulrich-teichert.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=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 \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).