Hi all,
I am using MIPS processor, with 256 MB RAM. currently I am using 128
M for drivers and 128 M for Kernel. I tried to allocate more memory
for Drivers,
surprisingly I got crash when I reduced kernel memory to 110 M. My
debugging took me to USB controller, which was not reset in
bootloader.
[Resending, I'm not sure where the previous email is lost.]
>From: kernelnewbies-bou...@nl.linux.org
>[mailto:kernelnewbies-bou...@nl.linux.org] On Behalf Of hiren panchasara
>Sent: Thursday, September 02, 2010 12:28 PM
>To: Prabhu nath
>Cc: kernelnewbies@nl.linux.org; techtrain...@tataelxsi.co.i
Hi Pavan...
On Thu, Sep 2, 2010 at 22:09, Pavan Savoy wrote:
> Hi,
>
> I use kill_pid in one of our drivers to signal a user-space daemon to
> perform a particular action (open-UART for instance), I recently ran
> into problems with permissions as to when a user with stranger UID
> started open u
Hi..
On Thu, Sep 2, 2010 at 14:11, John Mahoney wrote:
> I agree. I was trying to show an example of the minimal amount of
> work which must be accomplished by an interrupt handler with
> interrupts disabled before the work can be passed to a process
> context. I also think the threaded interru
Hi,
I use kill_pid in one of our drivers to signal a user-space daemon to
perform a particular action (open-UART for instance), I recently ran
into problems with permissions as to when a user with stranger UID
started open up a device, which internally calls the kill_pid in that
context, could not
Hi,
I want to know how the HC is reset @ the boot of the kernel.
Thanks & Reagrs,
Prabhu
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ
On Thu, Sep 2, 2010 at 2:36 AM, Mulyadi Santosa
wrote:
> On Thu, Sep 2, 2010 at 04:28, John Mahoney wrote:
>> I had read an article[1] a while back about a push in the real-time
>> kernel branch to make interrupt handlers scheduleable, but the article
>
> IIRC that's threaded interrupt handler...
Thanks a lot Prabhu for great explanation, comments in-line:
On Wed, Sep 1, 2010 at 10:02 PM, Prabhu nath wrote:
> Interrupt context is a loaded term. It is used for both top-half and
> bottom-half processing.
>
I need some more reading, will do that :)
> Linux defines two terms in the top-half
