ravikumar wrote:
Hello All ,
I've a few questions.
1. Lets suppose i've some critical section and it is synchronized with
locks. A thread came and it's execution is in the middle of
critical section, at this time an interrupt was occurred which also
executes critical section. As interrupts
Hello All ,
I've a few questions.
1. Lets suppose i've some critical section and it is synchronized with
locks. A thread came and it's execution is in the middle of critical
section, at this time an interrupt was occurred which also executes
critical section. As interrupts can't wait on any
I was just wondering when should round_jiffies() be used instead of
assigning the timer expiration with a specific jiffies value? Is the
round_jiffies() function call beneficial everywhere or just some
places?
-Stoyan G
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbi
David Woodhouse wrote:
> On Sun, 2008-07-06 at 11:09 +0200, Klaus Schmidinger wrote:
> > On 07/06/08 03:15, Oliver Endriss wrote:
> > > Jaswinder Singh wrote:
> > >> There's no point in this, since the user can use the BUILTIN_FIRMWARE
> > >> option to include arbitrary firmware files directly in t
Hi,
can a 64bit addresable PCI device be memory mapped (MMIO) above 4GB? or
linux will rather mapped it below 4gb?
i can't find in the kernel PCI probing where 64b devices are taken care
of..can someone plse provide some pointers?
thx
-jfs
--
To unsubscribe from this list: send an email with
"u
Hi David,
6 jul 2008 kl. 18.54 skrev David Woodhouse:
I don't think he has it. That's why he suggested a disassembler.
That's right. Sorry I was unclear. However, after some digging on
floppy backups from the past, I've found a DSP56k loader routine
that's probably close if not identical t
On Sun, 2008-07-06 at 21:08 +0530, Jaswinder Singh wrote:
> Hello Fredrik,
>
> On Sun, 2008-07-06 at 17:36 +0200, Fredrik Noring wrote:
> > Hi Jaswinder,
> >
> > 6 jul 2008 kl. 17.13 skrev Jaswinder Singh:
> > > Updated patch :
> > > http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=com
Hello Fredrik,
On Sun, 2008-07-06 at 17:36 +0200, Fredrik Noring wrote:
> Hi Jaswinder,
>
> 6 jul 2008 kl. 17.13 skrev Jaswinder Singh:
> > Updated patch :
> > http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=4f5b8828113ea857a7b590b7dbb8a5ee78103de4
> >
> > Thanks for you
Hi Jaswinder,
6 jul 2008 kl. 17.13 skrev Jaswinder Singh:
Updated patch :
http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=4f5b8828113ea857a7b590b7dbb8a5ee78103de4
Thanks for you comments.
Excellent. (Unfortunately I don't have access to the hardware to test
these ch
Hello Fredrik,
On Sun, 2008-07-06 at 15:36 +0200, Fredrik Noring wrote:
> Hi Jaswinder,
>
> 5 jul 2008 kl. 12.24 skrev Jaswinder Singh:
> > + for (i = 0; i < fw->size; i + 3) {
>
> Are you sure about "i + 3" in this loop? Isn't GCC complaining,
> something like "statement with no effect"?
>
On Sun, 2008-07-06 at 10:29 -0400, Devin Heitmueller wrote:
> Correct me if I'm wrong, but doesn't this also affect those
> distributions that consider kernels with binary firmware blobs to not
> be free software? Those distributions take the stance that the
> firmware must be loadable by userland
On Sun, Jul 6, 2008 at 7:17 AM, David Woodhouse <[EMAIL PROTECTED]> wrote:
> On Sun, 2008-07-06 at 11:09 +0200, Klaus Schmidinger wrote:
>> On 07/06/08 03:15, Oliver Endriss wrote:
>> > Jaswinder Singh wrote:
>> >> There's no point in this, since the user can use the BUILTIN_FIRMWARE
>> >> option t
Hi Jaswinder,
5 jul 2008 kl. 12.24 skrev Jaswinder Singh:
+ for (i = 0; i < fw->size; i + 3) {
Are you sure about "i + 3" in this loop? Isn't GCC complaining,
something like "statement with no effect"?
+Driver: ATARI_DSP56K - Atari DSP56k support
+
+File: dsp56k/bootstap.bin
+
+Lice
On Sun, 2008-07-06 at 11:09 +0200, Klaus Schmidinger wrote:
> On 07/06/08 03:15, Oliver Endriss wrote:
> > Jaswinder Singh wrote:
> >> There's no point in this, since the user can use the BUILTIN_FIRMWARE
> >> option to include arbitrary firmware files directly in the kernel image.
> >
> > NAK! Th
On 07/06/08 03:15, Oliver Endriss wrote:
Jaswinder Singh wrote:
There's no point in this, since the user can use the BUILTIN_FIRMWARE
option to include arbitrary firmware files directly in the kernel image.
NAK! This option allows to compile the firmware into the _driver_,
which is very useful
15 matches
Mail list logo
