OK - so after a bit more digging into things (and a poke by Mike) - I think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS - on 2007-06-28 this was added to Linus's tree:
http://lkml.org/lkml/2007/6/18/234
CONFIG_MTD_OOPS
tristate
On Fri 26 Jun 2009 13:42, David VomLehn pondered:
On Fri, Jun 26, 2009 at 10:39:50AM -0400, Robin Getz wrote:
OK - so after a bit more digging into things (and a poke by Mike) - I
think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS
On Sat 13 Jun 2009 14:59, Wolfgang Denk pondered:
Dear Russell King,
In message 20090613102642.gb7...@flint.arm.linux.org.uk you wrote:
The other way I've seen people read out crash messages is using a
debugger to dump the kernel's log buffer directly. That seems to work
as well as
On Thu 11 Jun 2009 08:48, Nicolas Ferre pondered:
Aras Vaichas :
* what is your boot time? What is the time from power-on to kernel
running, how long does the kernel take to run until init starts, and
how long does init take?
[snip]
That said, here are numbers from our not optimized demo
On 17 Oct 2007, after much discussion and debate, Mike added add two new
functions for reading the kernel log buffer (from kernel space).
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0b15d04af3dd996035d8fa81fc849d049171f9c3
The intention was for them to be used by
On Tue 30 Dec 2008 23:58, Jaya Kumar pondered:
On Tue, Dec 30, 2008 at 11:55 PM, Robin Getz rg...@blackfin.uclinux.org
wrote:
Yeah, I hadn't thought about spanning more than one gpio_chip. That's a good
point.
The currently posted code already supports spanning more than one gpio_chip
On Mon 29 Dec 2008 14:56, David Brownell pondered:
On Sunday 28 December 2008, Robin Getz wrote:
On Sat 27 Dec 2008 09:55, Jaya Kumar pondered:
I think that I would prefer 'group' or 'collection' to use some of
the words that David described things as 'ganged' or 'bus' or 'bank
On Sat 27 Dec 2008 09:55, Jaya Kumar pondered:
Oh, gosh darn it, how time has flown. My email above was to make sure
I have understood the feedback. I assume I should just get started on
implementing. Just to double check, the plan is:
- add bitmask support.
- add get_batch support
- improve
On Thu 9 Oct 2008 11:21, Adrian Bunk pondered:
On Tue, Oct 07, 2008 at 02:19:36PM -0700, Tim Bird wrote:
I've been thinking about a tool that might be useful
to track kernel size changes. I'm posting this
Request For Comments to get feedback, and determine
if this is something that would
On Wed 24 Sep 2008 13:06, Fundu pondered:
what about Non maskable interrupts ? disabling
interrupt won't have any effect on that
right ?
that really doesnt make sense by definition huh.
non-maskable means
they cant be masked.
yeah thats the point. i should have elaborated
10 matches
Mail list logo
