leads me into wondering
if there shouldn't be a generic framework for supporting this. So, instead of
using module_init, there might be some other macro that indicated that this
driver was to be initialized in a deferred, and optional, fashion.
--
David VomLehn, [EMAIL PROTECTED]
The opinions
.
--
David VomLehn, [EMAIL PROTECTED]
- - - - - Cisco- - - - -
This e-mail and any attachments may contain information which is confidential,
proprietary, privileged or otherwise protected by law. The information is solely
intended
Grant Likely wrote:
On Tue, Aug 12, 2008 at 06:30:54PM -0700, David VomLehn wrote:
Regardless of implementation, it seems to me that it could be of use for
some other embedded platforms. Any suggestions as to where it should go
in the tree? drivers/char? drivers/misc?
Depends on what
Tim Bird wrote:
David VomLehn wrote:
Our use case is:
1. We register a panic handler
2. The kernel panics and calls our panic handler
3. We register a function to log printk output
4. We print registers, stack, memory, and various other pieces of
information using standard kernel functions
. The cable settop boxes we develop have
over a hundred interrupt sources, typically run 250-300 threads, and have 192+
MiB of memory. For all that, we are very cost sensitive and are under constant
pressure to come up with reliable ways to save memory.
Parag
--
David VomLehn
--
To unsubscribe
not sufficient for this.
--
David VomLehn
- - - - - Cisco-
- - - -
This e-mail and any attachments may contain information which is confidential,
proprietary, privileged or otherwise protected by law. The information
Robin Getz wrote:
I'm just wondering what people using on standard embedded/headless/diskless
targets (which do not have hw random number generators) as a source of
entropy - since networking was removed as an entropy source circa 2.6.26
On my target:
root:/ cat
the
delay interval a tunable.
v1 Initial version
Signed-off-by: David VomLehn dvoml...@cisco.com
---
Documentation/kernel-parameters.txt | 10
arch/mips/configs/powertv_defconfig |2 +-
init/Kconfig| 12 ++
kernel/printk.c
Andi Kleen wrote:
VomLehn dvoml...@cisco.com writes:
History
v2 Wait for the preferred console rather than any console. Make the
delay interval a tunable.
CONFIG tunables are usually a bad idea. What should a binary distribution
kernel set? Better make it a boot option with a
Andi Kleen wrote:
On Sun, Apr 19, 2009 at 09:23:36AM -0700, David VomLehn wrote:
Andi Kleen wrote:
VomLehn dvoml...@cisco.com writes:
...
Also a setting to panic in this case might be useful, normally a system
without console is not very useful and needs to be rebooted anyways.
Umm, those
it makes sense where decent
people can see it.
--
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
in the USB world tell us that we have been lucky
to have had USB consoles work as long as they have.
--
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
console rather than any console. Make the
delay interval a tunable.
v1 Initial version
Signed-off-by: David VomLehn dvoml...@cisco.com
---
Documentation/kernel-parameters.txt |7 +++
arch/mips/configs/powertv_defconfig |2 +-
init/Kconfig| 12
if the console device is very slow to initialize or if
there is no console device, at all.
--
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
a significantly different approach to constructing boot
filesystems and we need a transitional period. In the interim, let's get
things working as they were.
David WoodhouseOpen Source Technology Centre
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe
Tue, Apr 21, 2009 at 10:37:41AM -0700, Linus Torvalds wrote:
On Tue, 21 Apr 2009, David VomLehn wrote:
What in the world are users going to do when they see a message about
output being lost? There is no way to recover the data and no way to
prevent it in the future. I don't think
On Tue, Apr 21, 2009 at 03:09:52PM -0400, Alan Stern wrote:
On Tue, 21 Apr 2009, David VomLehn wrote:
If somebody would like to suggest a programming interface (a waitqueue
perhaps?) by which the USB hub driver could send a notification when it
becomes idle, I could implement
pretty
sure they won't like for it to go missing under mysterious circumstances.
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
it
took to detect the console, if there was one.
An open question is whether we want to wait for all possible consoles or
whether we can proceed with as few as one.
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord
On Wed, Apr 22, 2009 at 11:40:09AM -0400, Alan Stern wrote:
On Tue, 21 Apr 2009, David VomLehn wrote:
...
There is one other possible gotcha to this approach. The code as I wrote it
is
bus-agnostic, i.e. it has no idea where the console is located. As far as
I know, the long time
On Wed, Apr 22, 2009 at 05:24:18PM -0400, Alan Stern wrote:
On Wed, 22 Apr 2009, Alan Cox wrote:
2.All devices have been probed
If we exit for reason 2, it means that no such device is present,
and we go on to the do the appropriate thing for that device class.
USB has no
On Fri, Apr 24, 2009 at 03:20:42PM -0400, Alan Stern wrote:
On Thu, 23 Apr 2009, David VomLehn wrote:
I'm still scratching my head, trying to figure out where I can tap into the
'USB notion of all devices that were present at boot time have been
probed'
that Alan mentions above, so I
On Fri, Apr 24, 2009 at 11:19:51PM +0100, Jamie Lokier wrote:
David VomLehn wrote:
This looks like a good plan and not hard to implement. It even should
be possible to fit USB disk drives into the scheme.
That would definitely rock.
How about this, perhaps in the generic device
On Tue, Jun 02, 2009 at 12:42:57PM -0500, James Bottomley wrote:
On Tue, 2009-06-02 at 13:29 -0400, Josh Boyer wrote:
Which leads me to suggest that it is at least worth having someone with an
embedded focus at KS to simply keep an eye out for impacts of generic
changes.
Feature parity
On Tue, Jun 02, 2009 at 11:29:46AM -0600, Grant Likely wrote:
On Tue, Jun 2, 2009 at 9:22 AM, James Bottomley
james.bottom...@hansenpartnership.com wrote:
Hi All,
We've got to the point where there are simply too many embedded
architectures to invite all the arch maintainers to the
(). We retrieve the last
n lines of the log before the crash and print it, so that gets captured
in the log, too.
Signed-off-by: David VomLehn dvoml...@cisco.com
---
drivers/char/Kconfig | 14 +++
drivers/char/Makefile |2 +
drivers/char/conslogger.c | 233
On Thu, Jun 11, 2009 at 02:52:38PM -0400, Robin Getz wrote:
On Thu 11 Jun 2009 13:53, David VomLehn pondered:
On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote:
...
Our kernel does crash, so we have to do this. I had submitted a patch a
while ago that tweaks emit_log_char
On Thu, Jun 11, 2009 at 11:22:57AM -0700, Tim Bird wrote:
David VomLehn wrote:
Our kernel does crash, so we have to do this. I had submitted a patch a
while ago that tweaks emit_log_char, but this was bounced, reasonably,
because it would be interferring with the great majority of people
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 2007-06-28 this was added to Linus's tree:
, it seems like it would
meet your need to give almost immediate feedback to users that the system is
alive.
--
David VomLehn
--
To unsubscribe from this list: send the line unsubscribe linux-embedded in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Thu, Nov 12, 2009 at 01:06:51PM -0500, Matt Mackall wrote:
On Wed, 2009-11-11 at 21:13 -0500, David VomLehn wrote:
Allows annotation of panics to include platform information. It's no big
deal to collect information, but way helpful when you are collecting
failure reports from a eventual
On Thu, Nov 12, 2009 at 02:50:41PM -0500, Paul Gortmaker wrote:
David VomLehn wrote:
Allows annotation of panics to include platform information. It's no big
deal to collect information, but way helpful when you are collecting
failure reports from a eventual base of millions of systems
On Tue, Nov 17, 2009 at 10:45:43AM -0500, Eric W. Biederman wrote:
...
Why not use the kdump hook? If you handle a kernel panic that way
you get enhanced reliability and full user space support. All in a hook
that is already present and already works.
I'm a big fan of avoiding reinvention of
On Tue, Nov 17, 2009 at 04:28:22PM -0800, Eric W. Biederman wrote:
David VomLehn dvoml...@cisco.com writes:
On Tue, Nov 17, 2009 at 10:45:43AM -0500, Eric W. Biederman wrote:
...
Why not use the kdump hook? If you handle a kernel panic that way
you get enhanced reliability and full
checkpatch doesn't know that the
printk facility level is passed into this function.
Signed-off-by: David VomLehn dvoml...@cisco.com
---
drivers/char/Kconfig | 14 +++
drivers/char/Makefile |2 +
drivers/char/conslogger.c | 249
Mike Frysinger wrote:
On Mon, Apr 12, 2010 at 02:35, David VomLehn wrote:
Provide functions for capturing console output for storage. The primary user
is likely to be embedded systems that don't have the storage for core dumps
but do have a need to log kernel panic information for later
David Delaney has a proof-of-concept of an idea of his which was
presented at the last CELF, which is basically to put the kernel and
loadable kernel modules closely enough together that you can avoid the
use of long jumps. He sees a better than 1% improvement in performance,
which we've
37 matches
Mail list logo
