[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6934efce0709201422r252b5fbbiaa1c7afdf938c7c6@mail.gmail.com>
Date: Thu, 20 Sep 2007 14:22:37 -0700
From: "Jared Hulbert" <jaredeh@...il.com>
To: "Rob Landley" <rob@...dley.net>
Cc: "Alexey Dobriyan" <adobriyan@...il.com>, linux-tiny@...enic.com,
"Tim Bird" <tim.bird@...sony.com>,
"linux kernel" <linux-kernel@...r.kernel.org>,
"CE Linux Developers List" <celinux-dev@...e.celinuxforum.org>,
"Michael Opdenacker" <michael@...e-electrons.com>
Subject: Re: [Announce] Linux-tiny project revival
> > I think that this idea is not worth it.
Don't use the config option then....
> My problem is that switching off printk is the single biggest bloat cutter in
> the kernel, yet it makes the resulting system very hard to support. It
> combines a big upside with a big downside, and I'd like something in between.
It's not such a big downside IMHO. You can support a kernel without
printk. Need to debug the kernel without printk? Use a JTAG
debugger...
If you have a system that actually configures out printk's, chances
are you don't have storage and output mechanisms to do much with the
messages anyway. Think embedded _products_ here. Sure the
development boards have serial, ethernet, and all that jazz but tens
of millions of ARM based gadgets don't.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists