From: fthain@telegraphics.com.au
To: "Kolbjørn Barmen" <linux-m68k@kolla.no>
Cc: mike <localgost@gmail.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
debian-68k@lists.debian.org
Subject: Re: bogl: don't know screen type 1
Date: Sat, 12 Sep 2009 20:24:31 +1000 (EST) [thread overview]
Message-ID: <alpine.LNX.2.00.0909122011590.6056@nippy.intranet> (raw)
In-Reply-To: <alpine.LNX.2.01.0909112137580.2168@halbrend.uninett.no>
On Fri, 11 Sep 2009, Kolbj?rn Barmen wrote:
> On Thu, 3 Sep 2009, mike wrote:
>
> > I tried to boot 2.6.29 or whatever... It was so slow compared to 2.4 i
> > donno what to say, except its crap. Not a surprise if gcc produces
> > crappier and crappier 68k binaries anyway. Why the hell isnt freescale
> > on top of this? Fuck damn they should be on top of this and the
> > 68050/70 the natami is trying out, and bloody include talent like Carl
> > S and Dave H that know what the heck the 68k, electronics, and the
> > amiga is about....
>
> For what it's worth - my m68k systems runs current linux kernel, 2.6.30,
> compiled with gcc 4.2.4 just fine, and I have not see any slow-down,
> apart from obvious things in bootup, like initiating udev, creating
> nodes and similar things that have nothing to do with kernel itself. I
> also make sure to compile my kernels with only the modules that makes
> sense for the hardware I run it on.
What happened to devtmpfs I wonder.
> My systems are one A1200 with Blizzard 1230III (030+882@50MHz) and 32MB
> RAM, one A1200 with Blizzard 1260 (060@50MHz) and 64MB RAM, and one Mac
> Quadra 910 (040@25MHz) with 64MB RAM. Oh and my build box, Aranym with a
> 040@100-180MHz depending on host at bootup, and for the time being,
> 256MB RAM (allthough, it is down ATM, fixing filesystem disaster after I
> somehow managed to launch aranym twice on same disk image :P)
Can't file locking prevent that? Sounds like a bug...
Finn
>
> The A1200 with Blizz1230III has been running more or less non-stop since
> 1997 with only a break now and then when moving between locations, being
> installed into new tower solutions, and infrequent kernel updates,
>
> I dont use debian though, I use gentoo since it gives me a tool
> (portage) to build packages the way I want them, stripped where needed,
> bloated for the things I care about. Almost everything is buildt -Os.
>
> So, in the end, I'm not so sure that what you complain about is for
> real.
>
> -- kolla
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-09-12 10:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 3:28 bogl: don't know screen type 1 mike
2009-08-31 12:06 ` Stephen R Marenka
2009-08-31 12:58 ` mike
2009-08-31 22:11 ` mike
2009-08-31 22:16 ` mike
2009-09-01 15:17 ` Stephen R Marenka
2009-09-03 1:16 ` mike
2009-09-03 1:22 ` mike
2009-09-03 9:50 ` Maxim Kuvyrkov
2009-09-03 16:41 ` mike
2009-09-11 20:01 ` Kolbjørn Barmen
2009-09-11 20:25 ` Geert Uytterhoeven
2009-09-12 10:24 ` fthain [this message]
2009-09-04 15:43 ` toolchain, was " Finn Thain
2009-09-05 1:08 ` Stephen R Marenka
2009-09-05 1:57 ` mike
2009-09-05 2:17 ` mike
2009-09-05 7:08 ` Petr Stehlik
2009-09-05 8:49 ` Ingo Jürgensmann
2009-09-06 5:07 ` Finn Thain
2009-09-05 13:31 ` Maxim Kuvyrkov
2009-09-05 16:00 ` mike
2009-09-06 10:00 ` Finn Thain
2009-09-06 2:37 ` toolchain Finn Thain
2009-09-06 23:09 ` toolchain Stephen R Marenka
2009-09-06 5:20 ` toolchain Finn Thain
2009-09-08 13:07 ` toolchain Finn Thain
2009-09-13 3:38 ` toolchain, was Re: bogl: don't know screen type 1 fthain
2009-09-13 5:01 ` Maxim Kuvyrkov
2009-09-14 10:37 ` fthain
2009-09-22 5:11 ` mike
2009-09-22 13:09 ` benchmarks, was Re: toolchain Finn Thain
2009-09-22 14:51 ` mike
2009-09-22 15:08 ` Geert Uytterhoeven
2009-09-28 14:00 ` toolchain, was Re: bogl: don't know screen type 1 mike
2009-09-28 14:26 ` debian installation Finn Thain
2009-09-28 14:44 ` mike
2009-09-29 9:45 ` mike
2009-09-29 22:23 ` Rolf Anders
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=alpine.LNX.2.00.0909122011590.6056@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@kolla.no \
--cc=linux-m68k@vger.kernel.org \
--cc=localgost@gmail.com \
/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