From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Andrews <jon@jonshouse.co.uk>
Cc: anish kumar <anish198519851985@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Stupid user with user-space questions, matrix LED driving with user space code only.
Date: Sun, 17 Feb 2013 18:05:57 -0800 [thread overview]
Message-ID: <20130218020557.GA27667@kroah.com> (raw)
In-Reply-To: <1361111844.14757.29.camel@jonspc>
On Sun, Feb 17, 2013 at 02:37:24PM +0000, Jonathan Andrews wrote:
> From a user perspective it seems a bit crap to have to change the kernel
> if you have a workload that preemption is harmful to.
> In the case of something like the Raspberry Pi changing the kernel if
> the distribution has not done the work for me sounds like real effort.
> The kernel is tied to binary obscurity from broadcom... To build I need
> a working cross compiler, toolchain, kernel sources, Pi specific patches
> then to get everything in the correct place on an SD card containing two
> filesystems. Its possible but its not going to "just work" at my skill
> level....
As you can not boot a kernel.org kernel on the RPI platform just yet,
there's very little that the kernel.org community can do here to help
you out. I suggest you go take this up with the developers whom you got
this specific kernel build from, there's nothing we can do here about
it.
Best of luck,
greg k-h
next prev parent reply other threads:[~2013-02-18 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 14:37 Stupid user with user-space questions, matrix LED driving with user space code only Jonathan Andrews
2013-02-17 6:22 ` anish kumar
2013-02-17 14:37 ` Jonathan Andrews
2013-02-17 15:05 ` anish kumar
2013-02-18 2:05 ` Greg KH [this message]
2013-02-18 5:06 ` Jonathan Andrews
2013-02-18 11:55 ` el es
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=20130218020557.GA27667@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anish198519851985@gmail.com \
--cc=jon@jonshouse.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.