gmane.os.netbsd.ports.sparc archive

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

Re: gem driver for sun4m
Sat, 18 Jul 2026 12:22:19 -0400
Erik LaBine <[email protected]> • #10255
Re: gem driver for sun4m
Sat, 18 Jul 2026 07:19:40 -0700
Jason Thorpe <[email protected]> • #10254
Re: gem driver for sun4m
Sat, 18 Jul 2026 11:56:03 +0200
Julian Coleman <[email protected]> • #10253
Re: gem driver for sun4m
Fri, 17 Jul 2026 07:03:28 -0700
Jason Thorpe <[email protected]> • #10252
Re: gem driver for sun4m
Fri, 17 Jul 2026 01:53:46 -0400
Erik LaBine <[email protected]> • #10251
Re: gem driver for sun4m
Wed, 15 Jul 2026 09:27:10 -0400
vom513 <[email protected]> • #10250
Re: gem driver for sun4m
Tue, 14 Jul 2026 18:45:36 -0700
Jason Thorpe <[email protected]> • #10249
gem driver for sun4m
Tue, 14 Jul 2026 17:58:34 -0500 (EST)
[email protected] • #10248
Re: Stopping the timekeeper clock (Was: New Timekeeper/RAM clock stops on power loss?)
Sat, 13 Jun 2026 19:59:53 +0200
Julian Coleman <[email protected]> • #10247
Re: Stopping the timekeeper clock (Was: New Timekeeper/RAM clock stops on power loss?)
Fri, 12 Jun 2026 12:59:17 -0400 (EDT)
Mouse <[email protected]> • #10246
Stopping the timekeeper clock (Was: New Timekeeper/RAM clock stops on power loss?)
Fri, 12 Jun 2026 18:39:52 +0200
Julian Coleman <[email protected]> • #10245
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Thu, 11 Jun 2026 08:14:43 -0500 (CDT)
"John D. Baker" <[email protected]> • #10244
Re: Building packages - qemu vs. CC etc.
Wed, 3 Jun 2026 09:38:02 +0200
Martin Husemann <[email protected]> • #10243
Re: Building packages - qemu vs. CC etc.
Tue, 2 Jun 2026 20:03:04 -0400 (EDT)
Mouse <[email protected]> • #10242
Building packages - qemu vs. CC etc.
Tue, 2 Jun 2026 16:35:06 -0400
vom513 <[email protected]> • #10241
Re: anyone have a theory why net boot of a SPARC20 hangs?
Thu, 28 May 2026 16:57:35 +0200
Julian Coleman <[email protected]> • #10240
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 18:58:00 -0400 (EDT)
Mouse <[email protected]> • #10239
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 21:27:15 +0200
Julian Coleman <[email protected]> • #10238
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 21:13:38 +0200
Julian Coleman <[email protected]> • #10237
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 27 May 2026 22:12:18 +0300
Valery Ushakov <[email protected]> • #10236
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 27 May 2026 13:57:58 -0500 (CDT)
"John D. Baker" <[email protected]> • #10235
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 13:44:38 -0400 (EDT)
Mouse <[email protected]> • #10234
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 13:02:22 -0400
Dennis Clarke <[email protected]> • #10233
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 27 May 2026 14:45:24 +0300
Valery Ushakov <[email protected]> • #10232
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 27 May 2026 06:19:53 -0500 (CDT)
"John D. Baker" <[email protected]> • #10231
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 09:07:10 +0200
Julian Coleman <[email protected]> • #10230
Re: anyone have a theory why net boot of a SPARC20 hangs?
Wed, 27 May 2026 09:50:28 +0300
Valery Ushakov <[email protected]> • #10229
anyone have a theory why net boot of a SPARC20 hangs?
Tue, 26 May 2026 23:29:15 -0400
Dennis Clarke <[email protected]> • #10228
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Mon, 25 May 2026 07:25:58 -0500 (CDT)
"John D. Baker" <[email protected]> • #10227
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Sat, 23 May 2026 20:45:47 -0500 (CDT)
"John D. Baker" <[email protected]> • #10226
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 22 May 2026 21:18:16 -0500 (CDT)
"John D. Baker" <[email protected]> • #10225
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 22 May 2026 14:22:46 -0500 (CDT)
"John D. Baker" <[email protected]> • #10224
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 15:26:54 -0500 (CDT)
"John D. Baker" <[email protected]> • #10223
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 10:48:55 -0500 (CDT)
"John D. Baker" <[email protected]> • #10222
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 15:50:32 +0100
David Brownlee <[email protected]> • #10221
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 08:52:02 -0500 (CDT)
"John D. Baker" <[email protected]> • #10220
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 07:17:05 -0500 (CDT)
"John D. Baker" <[email protected]> • #10219
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Fri, 1 May 2026 12:59:47 +0200
Martin Husemann <[email protected]> • #10218
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Thu, 30 Apr 2026 10:59:56 -0500 (CDT)
"John D. Baker" <[email protected]> • #10217
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 23:11:20 +0200
Martin Husemann <[email protected]> • #10216
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 16:54:28 -0400
Dennis Clarke <[email protected]> • #10215
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 13:49:46 -0500 (CDT)
"John D. Baker" <[email protected]> • #10214
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 11:50:19 -0500 (CDT)
"John D. Baker" <[email protected]> • #10213
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 14:36:58 +0200
Julian Coleman <[email protected]> • #10212
Re: netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Wed, 29 Apr 2026 10:02:14 +0200
Martin Husemann <[email protected]> • #10211
netbsd-11 vs. SUNW,qfe; hmeX: device timeout?
Tue, 28 Apr 2026 20:18:43 -0500 (CDT)
"John D. Baker" <[email protected]> • #10210
Re: cgfour patch
Mon, 27 Apr 2026 21:14:19 -0400
foo bar <[email protected]> • #10209
Re: cgfour patch
Mon, 27 Apr 2026 17:21:03 -0700
Jason Thorpe <[email protected]> • #10208
Re: cgfour patch
Mon, 27 Apr 2026 19:59:28 -0400
foo bar <[email protected]> • #10207
Re: cgfour patch
Mon, 27 Apr 2026 19:23:18 +0100
David Brownlee <[email protected]> • #10206
cgfour patch
Wed, 22 Apr 2026 15:31:00 -0400
foo bar <[email protected]> • #10205
Re: Kernel size (Was: Include DaynaPort by default in GENERIC?)
Sun, 19 Apr 2026 19:48:08 -0400
foo bar <[email protected]> • #10204
Re: Include DaynaPort by default in GENERIC?
Tue, 31 Mar 2026 13:46:43 -0400 (EDT)
Mouse <[email protected]> • #10203
Re: Include DaynaPort by default in GENERIC?
Tue, 31 Mar 2026 13:42:50 -0400 (EDT)
Mouse <[email protected]> • #10202
Re: Include DaynaPort by default in GENERIC?
Tue, 31 Mar 2026 11:32:10 +0200
Riccardo Mottola <[email protected]> • #10201
Re: Include DaynaPort by default in GENERIC?
Sun, 29 Mar 2026 22:32:31 -0700
Kevin Bowling <[email protected]> • #10200
Kernel size (Was: Include DaynaPort by default in GENERIC?)
Fri, 27 Mar 2026 12:53:55 +0100
Julian Coleman <[email protected]> • #10199
LACP/agr (Was: Include DaynaPort by default in GENERIC?)
Fri, 27 Mar 2026 12:20:18 +0100
Julian Coleman <[email protected]> • #10198
panic: alignment fault
Wed, 25 Mar 2026 18:21:37 -0400
Dennis Clarke <[email protected]> • #10197
Re: Include DaynaPort by default in GENERIC?
Wed, 25 Mar 2026 12:24:39 -0700
Jason Thorpe <[email protected]> • #10196
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 22:52:59 +0000
"mike.spooner.ux" <[email protected]> • #10195
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 22:07:14 +0000
"mike.spooner.ux" <[email protected]> • #10194
re: NetBSD/vax 11.0_RC2
Wed, 25 Mar 2026 16:52:20 +1100
matthew green <[email protected]> • #10193
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 21:19:43 -0400 (EDT)
Mouse <[email protected]> • #10192
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 20:54:06 -0400
Dave McGuire <[email protected]> • #10191
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 20:33:36 -0400 (EDT)
Mouse <[email protected]> • #10190
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 19:08:24 -0400
Dave McGuire <[email protected]> • #10189
Duplicated MACs [was Re: Include DaynaPort by default in GENERIC?]
Tue, 24 Mar 2026 18:50:01 -0400 (EDT)
Mouse <[email protected]> • #10188
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 18:40:01 -0400
Dennis Clarke <[email protected]> • #10187
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 18:37:11 -0400 (EDT)
Mouse <[email protected]> • #10186
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 18:35:56 -0400
Dennis Clarke <[email protected]> • #10185
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 15:35:31 -0700
Jason Thorpe <[email protected]> • #10184
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 17:47:14 -0400
Dave McGuire <[email protected]> • #10183
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 17:38:29 -0400
Dennis Clarke <[email protected]> • #10182
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 12:53:22 -0400
Dave McGuire <[email protected]> • #10181
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 12:42:59 -0400
Erik LaBine <[email protected]> • #10180
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 12:06:30 -0400
Dennis Clarke <[email protected]> • #10179
re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 16:20:36 +1100
matthew green <[email protected]> • #10178
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 21:16:04 -0700
Jason Thorpe <[email protected]> • #10177
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 20:50:46 -0700
Jason Thorpe <[email protected]> • #10176
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 20:34:47 -0700
Jason Thorpe <[email protected]> • #10175
Re: Include DaynaPort by default in GENERIC?
Tue, 24 Mar 2026 02:34:58 +0000
Ben Kallus <[email protected]> • #10174
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 22:02:06 -0400
foo bar <[email protected]> • #10173
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 18:13:38 -0700
Jason Thorpe <[email protected]> • #10172
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 20:19:44 -0400
foo bar <[email protected]> • #10171
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 12:43:51 -0400
Dave McGuire <[email protected]> • #10170
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 16:35:51 +0000
Ben Kallus <[email protected]> • #10169
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 11:39:25 -0400 (EDT)
Mouse <[email protected]> • #10168
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 10:24:15 -0500 (EST)
"[email protected] [email protected]" <[email protected]> • #10167
Re: Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 11:06:13 -0400
Dave McGuire <[email protected]> • #10166
Include DaynaPort by default in GENERIC?
Mon, 23 Mar 2026 15:00:33 +0000
Ben Kallus <[email protected]> • #10165
Re: NetBSD Sparc packages not available
Sun, 22 Feb 2026 19:32:56 -0500 (EST)
Mouse <[email protected]> • #10164
Re: NetBSD Sparc packages not available
Sun, 22 Feb 2026 19:28:47 -0500
Erik LaBine <[email protected]> • #10163
Re: NetBSD Sparc packages not available
Sun, 22 Feb 2026 22:46:45 +0100
Riccardo Mottola <[email protected]> • #10162
re: NetBSD Sparc packages not available
Mon, 23 Feb 2026 07:52:52 +1100
matthew green <[email protected]> • #10161
Re: NetBSD Sparc packages not available
Sun, 22 Feb 2026 08:33:36 -0500
Erik LaBine <[email protected]> • #10160
Re: NetBSD Sparc packages not available
Sun, 22 Feb 2026 06:13:29 -0500
Dennis Clarke <[email protected]> • #10159
NetBSD Sparc packages not available
Sat, 21 Feb 2026 23:09:09 -0500
Julien Savard <[email protected]> • #10158
Re: more binary packages and emacs status
Fri, 23 Jan 2026 22:41:47 +0300
Andrew Randrianasulu <[email protected]> • #10157
Re: more binary packages and emacs status
Fri, 23 Jan 2026 14:51:35 +0000 (UTC)
Chase Rayfield <[email protected]> • #10156
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.