7f20a9dcce3989 ("a.out: Remove the a.out implementation") in v6.1.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
uctions.
>
> True, but you won't be able to run any classic m68k binaries on ColdFire
> and the other way around, are you?
IIIRC if you use a proper subset of the user mode instructions, you
can create binaries that run on both.
Gr{oetje,eeting}s,
Geert
--
G
Hi Adrian,
On Wed, 18 Jun 2025 at 11:49, John Paul Adrian Glaubitz
wrote:
> On Wed, 2025-06-18 at 11:36 +0200, Geert Uytterhoeven wrote:
> > > I only know about Gentoo and Debian and both want to make the switch.
> >
> > Buildroot? Which is probably where the real produ
o and Debian and both want to make the switch.
Buildroot? Which is probably where the real product users (using Coldfire)
are hiding...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversation
Hi Adrian,
On Tue, 17 Jun 2025 at 12:13, John Paul Adrian Glaubitz
wrote:
> On Tue, 2025-06-17 at 11:59 +0200, Geert Uytterhoeven wrote:
> > > What's keeping us from creating an ABI v2 using either e_ident or e_flags
> > > from the ELF
> > > header so that we
Hi Adrian,
On Tue, 17 Jun 2025 at 11:48, John Paul Adrian Glaubitz
wrote:
> On Tue, 2025-06-17 at 09:40 +0200, Geert Uytterhoeven wrote:
> > > What's going to happen when Rust code becomes mandatory in key parts of
> > > the kernel
> > > and then we're u
el.home
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Hi Adrian,
On Tue, 17 Jun 2025 at 09:25, John Paul Adrian Glaubitz
wrote:
> On Tue, 2025-06-17 at 09:02 +0200, Geert Uytterhoeven wrote:
> > On Wed, 21 May 2025 at 04:15, John Klos wrote:
> > > Should Linux maintain a 32 bit platform that has alignment issues because
> >
c during the Linux kernel merge window
causes lots of delayed email :-(
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
wh
>
> Thanks, and you're welcome. Unfortunately, some people like Finn and Eero
> don't
> appreciate these efforts and seem to think that this all comes at zero costs.
Please calm down...
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Th
of
amd64/arm/arm64/ia64/i386/m68k/microblaze/mips(el)/powerpc/risvc/s390/sh/sparc
seem to use 0 (SYSV).
#define ELFOSABI_NONE 0
#define ELFOSABI_LINUX 3
Ah, parisc does. And C6x uses 0x40.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux
ined(TARGET_NIOS2)
#define ABI_LLONG_ALIGNMENT 4
#endif
which will probably become the next victim of the 64-bit little-endian
natural-alignment monoculture...
> And there will be a problem with binfmt_misc because we can't rely on
> the ELF signature to know which qemu-us
rro.h already has __packed for the various
AmigaOS structs, as that was needed for APUS (support for which was
removed from the kernel a long time ago).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- g
Hi Adrian,
On Fri, 13 Jun 2025 at 15:00, John Paul Adrian Glaubitz
wrote:
> On Fri, 2025-06-13 at 14:51 +0200, John Paul Adrian Glaubitz wrote:
> > On Fri, 2025-06-13 at 14:30 +0200, Geert Uytterhoeven wrote:
> > > So you change the default alignment, bump all so-versions in us
Hi Adrian,
On Fri, 13 Jun 2025 at 14:23, John Paul Adrian Glaubitz
wrote:
> On Fri, 2025-06-13 at 14:09 +0200, Geert Uytterhoeven wrote:
> > You are completely ignoring the last sentence I wrote...
>
> Because I am *extremely* tired of people heckling this discussion without
Hi Adrian,
On Fri, 13 Jun 2025 at 14:00, John Paul Adrian Glaubitz
wrote:
> On Fri, 2025-06-13 at 13:55 +0200, Geert Uytterhoeven wrote:
> > From its inception, Linux/m68k used an ABI compatible with SunOS,
> > which dates back to the MC68000, and was probably the most popu
not breaking the ABI between kernel and
user space, so changing that ABI is a no-go. What you do in the layers
above (in the kernel), or above (in userspace) is something different...
[1]
http://www.bitsavers.org/pdf/hp/9000_hpux/7.x/98794-90047_HP-UX_Portability_Guide_Sep89.pdf
Gr{oetje,eetin
Then the kernel has to take care of the translation.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
, as __alignof__(void *) = 2, but might still be useful
for anyone wanting to revive CRIS support ;-), I ran into Andreas'
explanation why the minimal alignment is still 2 bytes:
https://lore.kernel.org/all/87y3i442w1@linux-m68k.org/.
(TL;DR: SunOS started on 68000).
Gr{oetje,eeting}s
Hi Adrian,
On Tue, 20 May 2025 at 12:05, John Paul Adrian Glaubitz
wrote:
> On Tue, 2025-05-20 at 11:58 +0200, Geert Uytterhoeven wrote:
> > On Tue, 20 May 2025 at 10:38, John Paul Adrian Glaubitz
> > wrote:
> > > And I also don't understand why this is even
sted in new, "fancy" packages, just don't upgrade or install Debian
> Etch or similar. Changing the default alignment does not affect existing
> software.
What about existing software that is aware the minimum alignment is
2-bytes on m68k?
Gr{oetje,eeting}s,
is llvm-mos coping?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
atible, are
> they?
The syscall ABI is.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say &quo
Hi Adrian,
On Mon, 19 May 2025 at 09:54, John Paul Adrian Glaubitz
wrote:
> On Mon, 2025-05-19 at 09:42 +0200, Geert Uytterhoeven wrote:
> > I expect (the history of) the gcc sources would tell you more about
> > the default alignment on other (legacy UNIX) OSes supporting m68k..
SunOS5 (based on SVR4) no longer supported m68k.
I expect (the history of) the gcc sources would tell you more about
the default alignment on other (legacy UNIX) OSes supporting m68k...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux
Hi Adrian,
On Tue, 13 May 2025 at 10:21, John Paul Adrian Glaubitz
wrote:
> On Tue, 2025-05-13 at 09:55 +0200, Geert Uytterhoeven wrote:
> > On Mon, 12 May 2025 at 19:01, John Paul Adrian Glaubitz
> > wrote:
> > > Well, the official SysV ELF ABI by AT&T uses
Unix SVR4 ("AMIX") follow this?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists
rprised by the old SunOS's cc being able to fix
typoes in printed messages (sturct -> struct ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I cal
le amd64 changed both size and
alignment to 16.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I&
xperience: when it fails, in 50% of the cases the
system doesn't boot sufficiently far to use systemctl.
But all of that is irrelevant for an alignment discussion...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68
r suited to low memory systems
> > (and I'd consider even 256 MB on Amiga 'low memory' ...).
How many m68k systems actually have 256 MiB of RAM?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux
eof(struct baa) = 12
__alignof__(struct baa) = 4
???
Isn't the alignment of a struct the largest alignment of any of its members?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversa
er?
I guess there is code out there that checks for e.g. __mc68000__
and will start doing the wrong thing...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people
as simple as this or is
> > there a better solution?
>
> In this case, I would just recommend to use the proper format specifiers, see:
"%x" and "%o" always operate on unsigned values. There are no
format specifiers for signed hexadecimal and octal values, unlike
his does happen, ca. once per decade), and fixed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talkin
Hi Richard,
On Mon, Aug 28, 2023 at 10:17 PM Richard wrote:
> On August 28, 2023 11:26:58 AM UTC, Richard wrote:
> >On August 28, 2023 7:00:07 AM UTC, Geert Uytterhoeven
> >wrote:
> >>On Sun, Aug 27, 2023 at 11:36 AM James Le Cuirot
> >> wrote:
> >>
o declare such a structure with __attribute__((__packed__)),
and thus not only live with the overhead of doing unaligned accesses
from the D-cache, but also in emulating them in software...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyon
Hi Richard,
On Mon, Aug 28, 2023 at 1:27 PM Richard wrote:
> On August 28, 2023 7:00:07 AM UTC, Geert Uytterhoeven
> wrote:
> >On Sun, Aug 27, 2023 at 11:36 AM James Le Cuirot
> > wrote:
> >> On Sun, 2023-08-27 at 10:46 +1000, Finn Thain wrote:
> >> &
due to
non-natural alignment, please consider adding explicit padding"?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker.
ain
> does it cause them to accept a patch to make their struct layouts plain?
I guess you mean "ints" and "longs" instead of "shorts"?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@l
y be the only one still in use
> with Linux. Gentoo supports most of the architectures to some degree, and I'm
> not aware of any those having this issue.
AXIS CRIS was in the same (or a similar) boat, but support for CRIS
was dropped in Linux v4.17.
Gr{oetje,eeting}s,
.
Nice! (the reproducer, not the bug ;-)
Does it also fail on a very old kernel image you still have lying around?
Just to rule out a recent kernel bug.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In pe
.org/all/cabvgosmgpkktilku-ic0xgitdohep+3sb5x91hb8rnezfau...@mail.gmail.com
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'
Hi Michael,
On Tue, Apr 11, 2023 at 6:56 AM Michael Schmitz wrote:
> Am 11.04.2023 um 12:20 schrieb Finn Thain:
> > On Sun, 9 Apr 2023, Michael Schmitz wrote:
> >> Am 08.04.2023 um 00:06 schrieb Geert Uytterhoeven:
> >>> On Fri, Apr 7, 2023 at 3:58 AM Michael Schmi
Hi Finn,
On Sat, Apr 8, 2023 at 7:26 AM Finn Thain wrote:
> On Fri, 7 Apr 2023, Geert Uytterhoeven wrote:
> > > The only way I have found to alter dash's inclination to crash is to
> > > reboot. (I said previously I was unable to reproduce this in a single
> > >
t to be more subtle.)
That sounds like memory corruption somewhere else, e.g.
in the buffer cache...
Can you reproduce with CONFIG_DEBUG_SLAB=y?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
re to RAM, retrieve through a new /proc file?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just
c: .ei_osabi = ELF_OSABI,
arch/m68k/kernel/ptrace.c: .ei_osabi = ELF_OSABI,
arch/mips/kernel/ptrace.c: .ei_osabi = ELF_OSABI,
arch/mips/kernel/ptrace.c: .ei_osabi = ELF_OSABI,
arch/mips/kernel/ptrace.c: .ei_osabi = ELF_OSABI,
arch/nios2/kernel/ptra
Hi Mike,
On Mon, Feb 27, 2023 at 12:34 PM Mike Rapoport wrote:
> On Mon, Feb 27, 2023 at 10:42:34PM +1300, Michael Schmitz wrote:
> > Am 27.02.2023 um 21:26 schrieb Geert Uytterhoeven:
> > > FTR, here is the diff of the dmesg between good and bad:
> > >
> > &
r **cmdline_p)
> }
> #endif
>
> - paging_init();
> -
> #ifdef CONFIG_NATFEAT
> nf_init();
> #endif
>
--
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -
On Sun, Feb 26, 2023 at 12:02 PM Geert Uytterhoeven
wrote:
> On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
> wrote:
> > On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
> > > Looks surprisingly similar to the issue reported by Stan.
> > &g
Hi Adrian,
On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
wrote:
> On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
> > Looks surprisingly similar to the issue reported by Stan.
> > Do the mitigations given in
> > https:
on how much RAM you have ;-)
> Anyone else tried a recent kernel on their Amigas?
I really should start booting on real Amiga hardware again...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal
fix, and all m68k changes queued for
v6.3-rc1.
Alternatively, you'll have to wait for v6.3-rc1 (assumed Al's fixes
will land there, they're still not in linux-next), or until the fixes
have been backported to v6.2-stable. Or just create your own ;-)
Gr{oetje,eeting}s,
Hi Stan,
On Mon, Feb 6, 2023 at 9:31 PM Stan Johnson wrote:
> On 2/6/23 12:52 AM, Geert Uytterhoeven wrote:
> > On Mon, Feb 6, 2023 at 4:42 AM Stan Johnson wrote:
> >> On an SE/30 with 128 MiB memory, the latest Debian SID kernel
> >> (vmlinux-6.1.0-2-m68k), using D
it twice).
If you get to "K", you're almost at the end of arch/m68k/kernel/head.S,
and it is very likely the kernel C-code actually started.
Do you get any output using "debug earlyprintk" on the kernel command
line?
Gr{oetje,eeting}s,
Geert
n starting with a cold boot into Mac OS 7.5.5, but it
> > doesn't seem that that should make any difference for Linux. This
> > morning, after a cold boot, I saw two of the errors, while after a warm
> > boot, I saw four.
> Hmm - that might well indicate a hardware issue ra
does not need relocation, but bsr.l is 68020+ only.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just s
CC linux-m68k
On Mon, Jan 30, 2023 at 5:01 AM Stan Johnson wrote:
>
> Hello,
>
> I am seeing anywhere from zero to four of the following errors while
> booting Linux on 68030 systems and using sysvinit startup scripts:
>
> *** stack smashing detected ***: terminated
> Aborted
>
> I usually (but n
rd: 0783283d - 0800
... which does not match 0783283d?
Interestingly, this is the working case.
While the non-working case in your next email has
"ramdisk dest is 0x0f7f6794" and a matching
"initrd: 0f7f6794 - 1000".
/me confused even more...
Gr{oetje,eeting}s,
the scsi issue anyway. So
> you need a way to boot 5.19 without oops. Can you achieve that by altering
> the RAM configuration?
A monolithic Amiga kernel does not need an initrd, so it won't suffer
from the early crash.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoe
or both the good and the bad cases.
> But that's a little academic. I really wonder what makes the initrd at
> the end of the second RAM chunk fault. But e.g. the range
>
> 0f83283d - 1000
>
> extends one byte beyond what's mapped
>
> node 0: [mem 0x0
; omit "ignore_loglevel".
oh right, the "ignore_loglevel" is in the wrong location: it should be
located after the initrd.
In the screenshot you showed, "ignore_loglevel" was the last parameter,
which is fine.
Gr{oetje,eeting}s,
Geert
--
Geert
nning Amiboot with "-d"? That will print more info about
the used addresses, and will give you more time to read its output,
by waiting for a keypress before launching Linux.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux be
On Wed, Sep 7, 2022 at 11:42 AM Andreas Schwab wrote:
> On Sep 07 2022, Finn Thain wrote:
> > On Wed, 7 Sep 2022, Geert Uytterhoeven wrote:
> >> On Wed, Sep 7, 2022 at 12:09 AM Finn Thain wrote:
> >> > Regarding the oops that was originally reported, the kernel
oot=/dev/sda2 fb=false debug=mem BOOT_IMAGE=vmlinux-5.19.0-1-m68k
Hence Amiboot didn't provide the initrd...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations
ootloader or use a memfile to make use of this area!
That's not the reason why it crashed. Dropping that memory chunk is
expected (and good) behavior.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In
initrd?
> [0.00] Ignoring memory chunk at 0x780:0x80 before the first
> chunk
> [0.00] Fix your bootloader or use a memfile to make use of this area!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32
ly RAM, not
> address space for firmware or IO stuff.
As there are only two regions of Fast RAM, and the second one should
not be used as it is slow motherboard RAM, I think a memfile won't
make a difference.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There
.2 GiB of RAM.
https://lore.kernel.org/all/20220406201523.243733-1-laur...@vivier.eu
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker.
Hi Michael,
On Tue, Sep 28, 2021 at 6:06 AM Michael Schmitz wrote:
> On 27/09/21 21:11, Geert Uytterhoeven wrote:
> > On Mon, Sep 27, 2021 at 12:02 AM Michael Schmitz
> > wrote:
> >> I wouldn't hold my breath waiting for the 16 bit / 100 Mbit patches to
> &g
pen for
submission.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or som
gt; + pr_info("CFTABLE_ENTRY tuple:\n");
> + for (i=0; i + pr_cont("%hhx ", cftuple[i]);
> + if (i > 0 && !(i % 10)) pr_cont("\n");
> + }
> + pr_co
;t be used still isn't
> clear to me. Best leave the rest of the chunk list in address order.
Because the logic handling physical pages is basically a data structure
like (simplied) pages[address - base], with base the address of the first
chunk. So you can't have a negative index.
) used distinct code paths before the rewrite, but share
> much of the code now.
But the 68020 does have early termination pages, which map (IIRC) 2 MiB
at once. In the early days, 2 MiB should have been fine to map the kernel.
As that's the only mechanism used by head.S, perhaps the real reas
d.S in current kernels, mmu_map_tt() seems to
> contain the only special case for '020. But mmu_map_tt() is only used for
> Nubus slot space. So I'm none the wiser.
>
> Perhaps we need to look at head.S from before 1998 to figure out what
> motivated Penguin's '0
Hi Andreas,
On Mon, Mar 15, 2021 at 9:57 AM Andreas Schwab wrote:
> On Mär 15 2021, Geert Uytterhoeven wrote:
> > Two of the main differences between m68k platforms and the ia32 PC
> > platform are that (a) physical RAM doesn't always start at address
> > zero,
>
&
the ia32 PC
platform are that (a) physical RAM doesn't always start at address
zero, and (b) physical RAM isn't always contiguous. As supporting these
differences required non-linear mappings anyway, it was easy to support
rearranging blocks, too.
Gr{oetje,eeting}s,
covering a use case I don't see.
>
> With what you've reported, I can't see what use case this patch would
> have enabled either. For all I care, we should drop the three FAT
> related commits at the head of m68k-queue.
>
Thanks. Dropped.
Gr{oetje,eeting}s,
what problem is being fixed, or new feature added with the patch ?
> or am I missing something ?
TBH, I don't know. This patch came from the old Linux/m68k CVS.
If anyone feels it can be dropped, I can do so.
If anyone feels it is needed, please submit it upstream.
Gr{oetje,eeting
zeof/__alignof__/ should help.
Are 32-bit accesses to an address of the form 4 * n + 2 atomic?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I
a few out-of-tree kernel patches for Atari FAT
support as well, cfr. the top 3 commits of
https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/log/?h=m68k-queue
Needs some love from a knowledgeable person to send this upstream...
Gr{oetje,eeting}s,
e are
> > two issues:
>
> That's great. I didn't even know that X actually works :-).
Chunky 16 bpp mode...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with tec
n I just have the
> Display section in my xorg.conf.
>
> Can somebody share their working Amiga xorg.conf, please?
Sorry, no clue. Keyboard was broken with Xfbdev, too:
https://lists.x.org/archives/xorg-devel/2013-March/035831.html
Gr{oetje,eeting}s,
Geert
--
Geer
On Wed, Aug 12, 2020 at 10:30 AM Geert Uytterhoeven
wrote:
> There did exist a small AmigaOS emulator for Amiga UNIX, basically
> implementing a hunk loader and a few exec.library and dos.library calls.
> This was rumored to be sufficient to run e.g. the SAS C compiler.
> I tried it o
ux/m68k, and it could run a simple Hello World.
The only entrypoint you need to provide to run AmigaOS binaries is a
pointer to ExecBase at address 4. If TOS doesn't use that location for
something else, you can implement AmigaOS support.
Good luck! ;-)
Gr{oetje,eeting}s,
off-by: Greg Kroah-Hartman
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to jo
t; };
So now you have 5 bytes of padding if PERL_DEBUG_READONLY_OPS,
while I guess 1 would be sufficient?
What about
# ifdef PERL_DEBUG_READONLY_OPS
bool opslab_readonly;
U8 opslab_padding;
#else
U16opslab_padding;
# endif
?
Gr{oetje,eeting
lots begin here */
> };
Either invert the order of the two paddings, or replace them by a single one:
U8 _padding[3];
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with tec
Hi Adrian,
On Fri, Jun 19, 2020 at 10:20 AM John Paul Adrian Glaubitz
wrote:
> > On Jun 19, 2020, at 10:02 AM, Geert Uytterhoeven
> > wrote:
> >> On Thu, Jun 18, 2020 at 10:46 PM John Paul Adrian Glaubitz
> >> wrote:
> >>> On 6/18/20 12:10 PM, John
it would be better to add 3 bytes of explicit padding
instead one 16-bit quantity.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm
Hi Stefan,
On Tue, Mar 31, 2020 at 7:07 AM Stefan Reinauer
wrote:
> On Tue, Mar 10, 2020 at 1:15 AM Geert Uytterhoeven
> wrote:
> > On Tue, Mar 10, 2020 at 4:06 AM Stefan Reinauer
> > wrote:
> > > On Sun, Mar 8, 2020 at 3:43 AM Geert Uytterhoeven
> > >
Hi Stefan,
On Tue, Mar 10, 2020 at 4:06 AM Stefan Reinauer
wrote:
> On Sun, Mar 8, 2020 at 3:43 AM Geert Uytterhoeven
> wrote:
> > As well as trying to boot it with the BRP as primary memory (BRP first
> > in memfile) or sole memory (motherboard RAM disabled in memfile).
>
well as trying to boot it with the BRP as primary memory (BRP first
in memfile) or sole memory (motherboard RAM disabled in memfile).
> I will dig out my BRP tomorrow and see if it's actually detected in my A4000
> as well with current kernel versions.
Looking forward to these
river can do that, if CONFIG_MEMORY_HOTPLUG=y.
However, the latter depends on CONFIG_SPARSEMEM.
The early core code can just call memblock_add(), though.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.or
n the A2k again... maybe somebody has already built a Zorro card
> where we can mount a RasPi as a coprocessor, RAM disk, or control board?
> Ah, the possibilities, if only there was more time ;-)
Hey, I wanted to do something similar with a C64, and DMA from a Pi
through the C64 cartridge p
Hi Charlie,
On Wed, Dec 11, 2019 at 7:26 PM Karoly Balogh (Charlie/SGR)
wrote:
> On Wed, 11 Dec 2019, Geert Uytterhoeven wrote:
> > > I think I researched at some point, and in case of fatal errors in the
> > > process, there was a way to expose an AmigaDOS command line over
something has failed, and
> don't wait for it to boot into the other kernel.)
"newshell aux:" is your friend.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations w
000 remotely?
By pulling the keyboard clockline low? By controlling power?
Anything else?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myse
CC linux-ide, as people there may be more familiar with the quirks and
caveats of SD2IDE adapters
On Tue, Dec 10, 2019 at 3:56 PM Karoly Balogh (Charlie/SGR)
wrote:
> On Mon, 9 Dec 2019, Karoly Balogh (Charlie/SGR) wrote:
> > > It would be interesting to know if other people with A1200s have
> >
1 - 100 of 1024 matches
Mail list logo
