gmane.os.netbsd.ports.m68k archive

367 archived articles, newest first (page 1 of 4). Latest articles →

Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 2 Jul 2026 14:43:03 +0200
Geert Uytterhoeven <[email protected]> • #1753
Re: First successful cargo build - Re: Summary on what's blocking full Rust support on m68k
Sun, 07 Jun 2026 11:05:01 +0200
John Paul Adrian Glaubitz <[email protected]> • #1752
Re: problems with current on a 3/80
Tue, 26 May 2026 10:11:43 -0400
Jason Thorpe <[email protected]> • #1751
Re: problems with current on a 3/80
Tue, 26 May 2026 15:02:20 +0100
David Brownlee <[email protected]> • #1750
Re: First successful cargo build - Re: Summary on what's blocking full Rust support on m68k
Wed, 20 May 2026 13:20:24 +0200
John Paul Adrian Glaubitz <[email protected]> • #1749
Re: First successful cargo build - Re: Summary on what's blocking full Rust support on m68k
Wed, 20 May 2026 07:08:54 -0400
Jeffrey Walton <[email protected]> • #1748
First successful cargo build - Re: Summary on what's blocking full Rust support on m68k
Wed, 20 May 2026 10:36:55 +0200
John Paul Adrian Glaubitz <[email protected]> • #1747
Re: Summary on what's blocking full Rust support on m68k
Mon, 18 May 2026 15:03:24 +0200
John Paul Adrian Glaubitz <[email protected]> • #1746
Re: KGDB on virt68k?
Sat, 2 May 2026 16:21:06 -0700
Chris Hanson <[email protected]> • #1745
Re: KGDB on virt68k?
Sat, 2 May 2026 07:40:08 -0700
Jason Thorpe <[email protected]> • #1744
Re: KGDB on virt68k?
Sat, 2 May 2026 00:27:22 -0700
Chris Hanson <[email protected]> • #1743
Re: KGDB on virt68k?
Mon, 27 Apr 2026 15:56:32 -0700
Jason Thorpe <[email protected]> • #1742
Re: KGDB on virt68k?
Mon, 27 Apr 2026 15:45:17 -0700
Chris Hanson <[email protected]> • #1741
Re: KGDB on virt68k?
Sun, 26 Apr 2026 13:32:53 -0700
Chris Hanson <[email protected]> • #1740
Re: KGDB on virt68k?
Sun, 26 Apr 2026 13:31:07 -0700
Chris Hanson <[email protected]> • #1739
Re: KGDB on virt68k?
Sun, 26 Apr 2026 15:56:33 +0200
Martin Husemann <[email protected]> • #1738
Re: KGDB on virt68k?
Sun, 26 Apr 2026 04:56:32 -0700
Jason Thorpe <[email protected]> • #1737
KGDB on virt68k?
Sun, 26 Apr 2026 04:47:24 -0700
Chris Hanson <[email protected]> • #1736
Summary on what's blocking full Rust support on m68k
Thu, 23 Apr 2026 09:39:44 +0200
John Paul Adrian Glaubitz <[email protected]> • #1735
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Mon, 2 Mar 2026 11:11:00 +0100
Geert Uytterhoeven <[email protected]> • #1734
Upstream issue tracker for m68k created
Tue, 17 Feb 2026 09:49:54 +0100
John Paul Adrian Glaubitz <[email protected]> • #1733
Gcc issue with stack protector
Wed, 11 Feb 2026 16:40:34 +0100
Martin Husemann <[email protected]> • #1732
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 11 Feb 2026 11:41:49 +0100
Geert Uytterhoeven <[email protected]> • #1731
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Mon, 2 Feb 2026 11:53:51 +0100
Geert Uytterhoeven <[email protected]> • #1730
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 8 Jan 2026 07:45:18 +1100 (AEDT)
Finn Thain <[email protected]> • #1729
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 07 Jan 2026 09:19:59 +0100
"Arnd Bergmann" <[email protected]> • #1728
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 06 Jan 2026 22:30:50 +0100
John Paul Adrian Glaubitz <[email protected]> • #1727
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 6 Jan 2026 20:31:57 +0100
Geert Uytterhoeven <[email protected]> • #1726
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 06 Jan 2026 16:37:40 +0100
"Arnd Bergmann" <[email protected]> • #1725
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 06 Jan 2026 15:23:36 +0100
John Paul Adrian Glaubitz <[email protected]> • #1724
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 6 Jan 2026 14:34:02 +0100 (CET)
Kolbjørn Barmen <[email protected]> • #1723
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 06 Jan 2026 14:40:33 +0100
John Paul Adrian Glaubitz <[email protected]> • #1722
Re: New pmap status update
Fri, 19 Dec 2025 07:07:28 -0800
Jason Thorpe <[email protected]> • #1721
Re: New pmap status update
Mon, 15 Dec 2025 07:42:41 -0800
Jason Thorpe <[email protected]> • #1720
Re: New pmap status update
Mon, 15 Dec 2025 07:39:59 -0800
Jason Thorpe <[email protected]> • #1719
Re: New pmap status update
Tue, 16 Dec 2025 00:38:21 +0900
Izumi Tsutsui <[email protected]> • #1718
Re: New pmap status update
Tue, 16 Dec 2025 00:30:30 +0900
Izumi Tsutsui <[email protected]> • #1717
Re: New pmap status update
Tue, 16 Dec 2025 00:00:57 +0900
Izumi Tsutsui <[email protected]> • #1716
Re: New pmap status update
Sun, 14 Dec 2025 18:15:56 -0500
Jason Thorpe <[email protected]> • #1715
Re: New pmap status update
Sun, 14 Dec 2025 16:55:26 -0500
Jason Thorpe <[email protected]> • #1714
Re: New pmap status update
Sun, 14 Dec 2025 13:38:56 -0500
Jason Thorpe <[email protected]> • #1713
Re: New pmap status update
Sun, 14 Dec 2025 23:25:51 +0900
Izumi Tsutsui <[email protected]> • #1712
Re: New pmap status update
Sat, 29 Nov 2025 14:52:19 -0800
Jason Thorpe <[email protected]> • #1711
Re: New pmap status update
Sat, 29 Nov 2025 13:17:39 -0800
Jason Thorpe <[email protected]> • #1710
Re: New pmap status update
Sat, 29 Nov 2025 10:20:19 -0800
Jason Thorpe <[email protected]> • #1709
Re: New pmap status update
Sun, 30 Nov 2025 02:46:27 +0900
Izumi Tsutsui <[email protected]> • #1708
New pmap status update
Thu, 27 Nov 2025 17:59:27 -0800
Jason Thorpe <[email protected]> • #1707
Re: m68k cacheops header -- some questions
Fri, 14 Nov 2025 13:54:03 +0100
Hauke Fath <[email protected]> • #1706
Re: m68k cacheops header -- some questions
Fri, 14 Nov 2025 21:28:03 +0900
Izumi Tsutsui <[email protected]> • #1705
Re: New pmap module for m68k
Thu, 13 Nov 2025 18:52:16 +0000
David Brownlee <[email protected]> • #1704
Re: New pmap module for m68k
Thu, 13 Nov 2025 19:06:06 +0100
Romain Dolbeau <[email protected]> • #1703
Re: New pmap module for m68k
Thu, 13 Nov 2025 09:47:26 -0800
Jason Thorpe <[email protected]> • #1702
Re: New pmap module for m68k
Thu, 13 Nov 2025 18:01:52 +0100 (CET)
Kolbjørn Barmen <[email protected]> • #1701
Re: Current status of new m68k pmap
Thu, 13 Nov 2025 09:01:34 -0800
Jason Thorpe <[email protected]> • #1700
Current status of new m68k pmap
Fri, 14 Nov 2025 00:22:43 +0900
Izumi Tsutsui <[email protected]> • #1699
Re: New pmap module for m68k
Thu, 13 Nov 2025 10:05:50 +0100
Romain Dolbeau <[email protected]> • #1698
Re: New pmap module for m68k
Wed, 12 Nov 2025 10:15:03 -0800
Jason Thorpe <[email protected]> • #1697
Re: New pmap module for m68k
Tue, 11 Nov 2025 00:33:25 +0900
Tetsuya Isaki <[email protected]> • #1696
Re: New pmap module for m68k
Mon, 10 Nov 2025 23:55:42 +0900
Izumi Tsutsui <[email protected]> • #1695
Re: New pmap module for m68k
Mon, 10 Nov 2025 06:02:05 -0800
Jason Thorpe <[email protected]> • #1694
Re: New pmap module for m68k
Mon, 10 Nov 2025 08:10:14 +0100
Romain Dolbeau <[email protected]> • #1693
Re: New pmap module for m68k
Sun, 9 Nov 2025 14:37:41 -0800
Jason Thorpe <[email protected]> • #1692
Re: New pmap module for m68k
Mon, 10 Nov 2025 05:07:06 +0900
Izumi Tsutsui <[email protected]> • #1691
Re: New pmap module for m68k
Sun, 9 Nov 2025 11:03:45 -0800
Jason Thorpe <[email protected]> • #1690
Re: New pmap module for m68k
Sun, 9 Nov 2025 19:34:48 +0100
Romain Dolbeau <[email protected]> • #1689
New pmap module for m68k
Sun, 9 Nov 2025 10:18:22 -0800
Jason Thorpe <[email protected]> • #1688
m68k cacheops header -- some questions
Sun, 26 Oct 2025 09:33:31 -0700
Jason Thorpe <[email protected]> • #1687
Re: virt68k live-image
Sun, 12 Oct 2025 21:46:17 -0700
Chris Hanson <[email protected]> • #1686
virt68k live-image
Sun, 12 Oct 2025 19:04:50 -0700
Chris Hanson <[email protected]> • #1685
Re: Porting to my custom 030 board
Wed, 1 Oct 2025 11:19:32 -0700
Jason Thorpe <[email protected]> • #1684
Re: Porting to my custom 030 board
Thu, 2 Oct 2025 02:54:27 +0900
Izumi Tsutsui <[email protected]> • #1683
Re: Porting to my custom 030 board
Wed, 1 Oct 2025 16:19:48 +0200
Hauke Fath <[email protected]> • #1682
Re: Porting to my custom 030 board
Wed, 1 Oct 2025 07:26:28 -0700
Jason Thorpe <[email protected]> • #1681
Re: Porting to my custom 030 board
Wed, 1 Oct 2025 11:59:01 +0100
Lawrence Manning <[email protected]> • #1680
Re: Porting to my custom 030 board
Tue, 30 Sep 2025 16:58:50 -0700
Chris Hanson <[email protected]> • #1679
Re: Build failures for Atari ramdisk images
Fri, 19 Sep 2025 22:35:37 +0900
Izumi Tsutsui <[email protected]> • #1678
Build failures for Atari ramdisk images
Fri, 19 Sep 2025 08:59:08 +0200
Martin Husemann <[email protected]> • #1677
Re: atari "prepare" floppy is overflowing
Thu, 3 Jul 2025 12:46:02 +0200
Martin Husemann <[email protected]> • #1676
Re: atari "prepare" floppy is overflowing
Thu, 3 Jul 2025 11:30:36 +0100
David Brownlee <[email protected]> • #1675
atari "prepare" floppy is overflowing
Mon, 30 Jun 2025 12:42:53 +0200
Martin Husemann <[email protected]> • #1674
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Mon, 23 Jun 2025 09:13:32 +0200
Geert Uytterhoeven <[email protected]> • #1673
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Mon, 23 Jun 2025 08:34:39 +0200
John Paul Adrian Glaubitz <[email protected]> • #1672
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Mon, 23 Jun 2025 01:13:08 +0300
Eero Tamminen <[email protected]> • #1671
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 08:57:48 -0700
Jason Thorpe <[email protected]> • #1670
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 15:56:59 +1000
Greg Ungerer <[email protected]> • #1669
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 15:31:58 +1000 (AEST)
Finn Thain <[email protected]> • #1668
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 10:18:04 +1000
Greg Ungerer <[email protected]> • #1667
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 08:29:43 +1000 (AEST)
Finn Thain <[email protected]> • #1666
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 08:17:39 +1000 (AEST)
Finn Thain <[email protected]> • #1665
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Thu, 19 Jun 2025 08:16:01 +1000 (AEST)
Finn Thain <[email protected]> • #1664
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 22:59:53 +1000
Greg Ungerer <[email protected]> • #1663
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 14:57:15 +0200
John Paul Adrian Glaubitz <[email protected]> • #1662
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 14:54:08 +0200
Geert Uytterhoeven <[email protected]> • #1661
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 14:27:22 +0200
John Paul Adrian Glaubitz <[email protected]> • #1660
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 22:21:49 +1000
Greg Ungerer <[email protected]> • #1659
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 20:51:45 +1000 (AEST)
Finn Thain <[email protected]> • #1658
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 12:04:01 +0200
John Paul Adrian Glaubitz <[email protected]> • #1657
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 11:56:26 +0200
Geert Uytterhoeven <[email protected]> • #1656
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 11:49:15 +0200
John Paul Adrian Glaubitz <[email protected]> • #1655
Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Wed, 18 Jun 2025 11:36:52 +0200
Geert Uytterhoeven <[email protected]> • #1654
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.