On Fri, 2007-06-15 at 14:40 +0200, Andi Kleen wrote:
> > That is broken on all non-x86 architectures,
> It cannot be broken, it just might be somewhat slower
No, Andi. It's broken.
We're speaking of a 32-bit ioctl compat routine. I would say it's more
than 'convention' that the structure used
On 6/15/07, Bernd Paysan <[EMAIL PROTECTED]> wrote:
On Thursday 14 June 2007 20:55, Dmitry Torokhov wrote:
> It does not matter. GPL v2 and later can be reduced to v2 by
> recepient.
And expanded by the next recipient to GPLv2 or later, as long as the first
recipient does not make a substantial
On Friday 15 une 2007 14:09, David Howells wrote:
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Why does it break them? It should just make them a little slower.
>
> Not all CPUs deliver recoverable misalignment exceptions.
These CPUs are too broken to run Linux then.
> > The network code require
> That is broken on all non-x86 architectures,
It cannot be broken, it just might be somewhat slower
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
P
On Friday 15 June 2007, Matthew Wilcox wrote:
> You're relying on compat_[us]64 being only used in structures which are
> already packed. If someone uses them in a non-packed struct, they won't
> decrease the alignment. I think it would be more effective to specify
> it as:
>
> __attribute__((al
On Thu, Jun 14, 2007 at 11:31:13PM -0300, Alexandre Oliva wrote:
> I know. Neither will Linus. But he says he chose GPLv2 such that he
> could, and the v2 is better than v3 in this regard. What's wrong with
> this picture?
I'm sure it's a rethorical question - but what is wrong is that
imho the
On 6/15/07, Bernd Paysan <[EMAIL PROTECTED]> wrote:
On Thursday 14 June 2007 19:20, Paulo Marques wrote:
> Watching the output of the first grep without "wc -l" shows that,
> although it is not 100% accurate, it is still ok just to get a rough
> estimate.
>
> So yes, ~6300 files are definitely mo
Hi!
> > Your proposal is similar to one I made to some Japanese developers
> > earlier this year. I was more modest, proposing that we
> >
> > - add an enhanced printk
> >
> > xxprintk(msgid, KERN_ERR "some text %d\n", some_number);
> Maybe a stupid idea but why do we want to assign these
* Michael Poole <[EMAIL PROTECTED]> wrote:
> > However, since the signing is an automated process it cannot
> > generate a "new" work - at least, not under the laws of the US - so
> > the signature itself cannot have a copyright at all.
[...]
>
> I do not suggest that copyright subsists in the
> It's the _location_ which is wrong;
As long as everybody using it sees the attribute packed it is not wrong at
all. ABIs are just a convention, not a law.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
On Fri, 2007-06-15 at 06:11 -0600, Matthew Wilcox wrote:
> You're relying on compat_[us]64 being only used in structures which are
> already packed.
In which case the whole exercise is pointless, on account of the
structure being already packed. It was _already_ laid out the same on
32-bit and 64
On Fri, 2007-06-15 at 14:29 +0200, Ingo Molnar wrote:
> the argument is quite strong that the linking of two independent works
> is "mere aggregation" as well. (as long as they are truly separate
> works)
You think so?
If even linking was considered 'mere aggregation on a volume of a
storage o
On Thu, 2007-06-14 at 19:56 +, Pavel Machek wrote:
>
> noapic/nolapic will not help with video issue. try s2ram from
> suspend.sf.net.
Also there is (unashamed plug)
http://people.freedesktop.org/~hughsient/quirk/
Richard.
-
To unsubscribe from this list: send the line "unsubscribe linux-k
Hi!
> >> resume from suspend to ram doesn't work for my laptop and never
> >> has. So, this is not a regression.
> [...]
> > Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
> > too.
>
> With the proprietary nvidia module, the laptop resumes, but the screen
> stays black. Mea
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 240978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start
Hi!
> I also don't care about the details of how it gets
> implemented, but when the AA people have a working
> implementation, and the SELinux people are strongly
> opposed to the concept, I don't see any advantage in
Actually, SELinux people 'liked' the concept -- they are willing to
extend
* David Woodhouse <[EMAIL PROTECTED]> wrote:
> > For example i'd say VMWare's ESX bin-only module is likely derived
> > from the Linux kernel and should be distributed under the GPL, but
> > that for example the ATI and nvidia drivers, although being a large
> > PITA for all of us, are possibl
would be interesting if teher was also a document about XFS that is more
suitable for some kind of use, and maybe reiserFS...
>
> Nice three documents with many numbers:
>
> http://blogs.sun.com/ontherecord/entry/now_available_three_new_solaris
>
> kloczek
> --
> --
On Fri, 15 June 2007 00:46:46 +0200, DervishD wrote:
>
> When do you think it will be included mainstream?
I am horrible at predictions, doubly so when concerning the future.
Several people believe it is good enough for -mm inclusion now. So it
might make it for 2.6.23 or 2.6.24.
Jörn
--
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a Disk Storage Driver for the PS3:
- Implemented as a block device driver with a dynamic major
- Disk names (and partitions) are of the format ps3d%c(%u)
- Uses software scatter-gather with a 64 KiB bounce buffer as the hypervisor
doesn't
On Fri, Jun 15, 2007 at 11:31:37AM +0200, Arnd Bergmann wrote:
> One common problem with 32 bit system call and ioctl emulation
> is the different alignment rules between i386 and 64 bit machines.
> A number of drivers work around this by marking the compat
> structures as 'attribute((packed))', wh
Add support for storage devices to the device probe code.
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
Changes since previous submission:
o use msleep() instead of schedule_timeout()
arch/powerpc/platforms/ps3/device-init.c | 28
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a FLASH ROM Storage Driver for the PS3:
- Implemented as a misc character device driver
- Uses a fixed 256 KiB buffer allocated from boot memory as the hypervisor
requires the writing of aligned 256 KiB blocks
CC: Geoff Levand <[EMAIL PROTE
Preallocate 256 KiB of bootmem memory for the PS3 FLASH ROM storage driver.
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/ps3/setup.c | 19 ++-
include/asm-powerpc/ps3.h |1 +
2 files
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add storage driver core support for the PS3.
PS3 storage devices are a special kind of PS3 system bus devices
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
Changes since previous submission:
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a CD/DVD/BD Storage Driver for the PS3:
- Implemented as a SCSI device driver
- Uses software scatter-gather with a 64 KiB bounce buffer as the hypervisor
doesn't support scatter-gather
CC: Geoff Levand <[EMAIL PROTECTED]>
Signed-off-by: Ge
Hi,
This is the second submission of the new PS3 storage drivers:
[1] ps3: Preallocate bootmem memory for the PS3 FLASH ROM storage driver
[2] ps3: Storage Driver Core
[3] ps3: Storage device registration routines.
[4] ps3: Disk Storage Driver
[5] ps3: ROM Storage Driver
[6] ps
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Why does it break them? It should just make them a little slower.
Not all CPUs deliver recoverable misalignment exceptions. This is probably
particularly true of NOMMU-mode archs where the CPU designed may have taken
the view that if a data exception is de
* Rob Landley <[EMAIL PROTECTED]> wrote:
> > uhm, so if the MPAA and the RIAA pays for another nice piece of
> > legislation that extends the power of copyright owners, do you find
> > it morally justified to use those powers, as long as it's argued to
> > be in favor of some long-term goal th
Daniel Hazelton writes:
> Following your logic it would be a "failure to distribute the source code for
> a work".
>
> However, since the signing is an automated process it cannot generate a "new"
> work - at least, not under the laws of the US - so the signature itself
> cannot have a copyrigh
On Friday 15 June 2007 13:49, Paulo Marques wrote:
> I've contributed some code for the kernel (unlike yourself, AFAICT), and
> believe me, I did so under GPL v2. The COPYING file is pretty much self
> explanatory, so I didn't need to add any explicit license statement to
> my code.
It's not, it's
On Friday 15 June 2007, Andi Kleen wrote:
>
> On Friday 15 June 2007 11:31:37 Arnd Bergmann wrote:
> > One common problem with 32 bit system call and ioctl emulation
> > is the different alignment rules between i386 and 64 bit machines.
> > A number of drivers work around this by marking the compa
On Sat, 2007-06-09 at 20:08 -0700, Andrew Morton wrote:
> On Sat, 9 Jun 2007 22:59:49 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > Hmm, how's 2.6.22-rc4-mm2 doing on the Vaio?
>
> People would have heard if it was busted ;)
Just found a brown paperbag bug in the resume patch log
On Fri, 15 June 2007 12:59:27 +0400, Evgeniy Polyakov wrote:
> On Sun, Jun 03, 2007 at 08:44:29PM +0200, Jörn Engel ([EMAIL PROTECTED])
> wrote:
> > --- /dev/null 2007-03-13 19:15:28.862769062 +0100
> > +++ linux-2.6.21logfs/fs/logfs/dir.c2007-06-03 19:54:55.0
> > +0200
>
>
> because you can solder off the ROM from the Tivo and can put in a new
> ROM with another bootloader that does not check the SHA1 key. Tivo puts
Then you've committed an offence because of the SHA1 key removal. Tivo
deliberately create a system where removal of the ROM is an offence
(sometimes
On Fri, 2007-06-15 at 13:55 +0200, Andi Kleen wrote:
> On Friday 15 June 2007 11:31:37 Arnd Bergmann wrote:
> > One common problem with 32 bit system call and ioctl emulation
> > is the different alignment rules between i386 and 64 bit machines.
> > A number of drivers work around this by marking t
On Fri, 2007-06-15 at 13:49 +0200, Ingo Molnar wrote:
> i fully support the notion you articulate, that whether bin-only modules
> are part of a derivative work of the kernel or whether they are
> independent works is not an automatic thing at all. The answer is: "it
> depends, talk to your lawy
On Friday 15 June 2007 03:49, Rob Landley wrote:
> (Right now, nobody EXCEPT the FSF has the right to sue somebody to
> enforce the license terms on something like gcc. Do you find that a
> comforting thought?)
Have you ever signed a copyright transfer agreement to the FSF? Obviously
not, becaus
On Friday 15 June 2007 11:31:37 Arnd Bergmann wrote:
> One common problem with 32 bit system call and ioctl emulation
> is the different alignment rules between i386 and 64 bit machines.
> A number of drivers work around this by marking the compat
> structures as 'attribute((packed))', which is not
Neil Brown wrote:
>
>> while I consider zfs to be ~80% hype, one advantage it could have (but I
>> don't know if it has) is that since the filesystem an raid are integrated
>> into one layer they can optimize the case where files are being written
>> onto unallocated space and instead of read
* David Woodhouse <[EMAIL PROTECTED]> wrote:
> Who cares about whether the module is a derivative work? That's only
> relevant when you distribute the module as a separate work. When you
> ship a combined work including both the kernel and the module in
> question, it's a _whole_ lot easier to
Bernd Paysan wrote:
On Thursday 14 June 2007 19:20, Paulo Marques wrote:
Watching the output of the first grep without "wc -l" shows that,
although it is not 100% accurate, it is still ok just to get a rough
estimate.
So yes, ~6300 files are definitely more than a couple ;)
I knew I shouldn't
On Fri, Jun 15, 2007 at 11:22:21AM +0200, Carsten Otte wrote:
> Jared Hulbert wrote:
> >>If you're interrested in using the later for xip without
> >>struct page, I would volounteer to go ahead and implement this?
> >I'm very interested in this.
> Good. Let me see if I can come up with a patch on t
* Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> > Do they have to provide a ROM burner if the ROM is socketed rather
> > than soldered into place?
>
> Of course not. They just can't impose restrictions on your obtaining
> a ROM burner and doing the work yourself.
do you realize that you have
Le Ven 15 juin 2007 12:53, Jesper Juhl a écrit :
> On 15/06/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
>> >> > by your argument, the user has some "right to modify the
>> software", on
>> >> > that piece of hardware it bought which had free software on it,
>> correct?
>> >>
>> >> Yes. This me
* Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> > by your argument, the user has some "right to modify the software",
> > on that piece of hardware it bought which had free software on it,
> > correct?
>
> Yes. This means the hardware distributor who put the software in
> there must not place
On 06/15, Rafael J. Wysocki wrote:
>
> +static void freeze_task(struct task_struct *p)
> +{
> if (!freezing(p)) {
> rmb();
> if (!frozen(p)) {
> set_freeze_flag(p);
> - if (p->state == TASK_STOPPED)
> -
On Fri, Jun 15 2007, Tejun Heo wrote:
> SCSI marks internal commands with REQ_PREEMPT and push it at the front
> of the request queue using blk_execute_rq(). When entering suspended
> or frozen state, SCSI devices are quiesced using
> scsi_device_quiesce(). In quiesced state, only REQ_PREEMPT req
On Fri, June 15, 2007 10:01, Jan Engelhardt wrote:
>
> On Jun 14 2007 14:52, markus reichelt wrote:
>>* Matthew <[EMAIL PROTECTED]> wrote:
>>
>>> I read that now loop devices are being created on demand, which
>>> obviously (still) not works
>>
>>yes, someone thought this was a good idea :(
>
> It
On Fri, 15 June 2007 13:03:57 +0400, Evgeniy Polyakov wrote:
> On Sun, Jun 03, 2007 at 08:46:04PM +0200, Jörn Engel ([EMAIL PROTECTED])
> wrote:
> > --- /dev/null 2007-03-13 19:15:28.862769062 +0100
> > +++ linux-2.6.21logfs/fs/logfs/gc.c 2007-06-03 19:18:57.0 +0200
>
> Number of bu
SCSI marks internal commands with REQ_PREEMPT and push it at the front
of the request queue using blk_execute_rq(). When entering suspended
or frozen state, SCSI devices are quiesced using
scsi_device_quiesce(). In quiesced state, only REQ_PREEMPT requests
are processed. This is how SCSI blocks
On Fri, 15 June 2007 12:37:32 +0400, Evgeniy Polyakov wrote:
> On Sun, Jun 03, 2007 at 08:38:46PM +0200, Jörn Engel ([EMAIL PROTECTED])
> wrote:
> > This round the patch is split into file-sized hunks. There actually
> > seem to be kernel developers not manly enough to digest 6000+ lines of
> > c
On Jun 11 2007 13:51, H. Peter Anvin wrote:
>Jan Engelhardt wrote:
>> (yay, 3.09 bogomips and a totally incapable processor :p)
>> Have not tried more recent kernels yet though.
>
>Too bad I don't still have access to the 0.59 bogomips "double sigma"
>386 machine that had the dubious honor of bein
On Fri, 15 Jun 2007 12:43:01 +0200, Arnd Bergmann wrote:
> On Friday 15 June 2007, Mikael Pettersson wrote:
> > > --- linux-2.6.22-rc4-fixed/fs/quota.c.orig=A0=A0=A0=A02007-06-14 15:55:=
> 26.0 +0400
> > > +++ linux-2.6.22-rc4-fixed/fs/quota.c=A02007-06-14 19:50:13.0 +=
> 0400
> > .
On Fri, Jun 15 2007, Tejun Heo wrote:
> SCSI marks internal commands with REQ_PREEMPT and push it at the front
> of the request queue using blk_execute_rq(). When entering suspended
> or frozen state, SCSI devices are quiesced using
> scsi_device_quiesce(). In quiesced state, only REQ_PREEMPT req
On Fri, 2007-06-15 at 12:43 +0200, Arnd Bergmann wrote:
> On Friday 15 June 2007, Mikael Pettersson wrote:
> > > --- linux-2.6.22-rc4-fixed/fs/quota.c.orig2007-06-14
> > > 15:55:26.0 +0400
> > > +++ linux-2.6.22-rc4-fixed/fs/quota.c 2007-06-14 19:50:13.0 +0400
> > ...
> > > +#i
On 15/06/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
>> > by your argument, the user has some "right to modify the
software", on
>> > that piece of hardware it bought which had free software on it,
correct?
>>
>> Yes. This means the hardware distributor who put the software in
>> there must n
On Fri, 15 Jun 2007, Jiri Kosina wrote:
> please try the patch below (against 2.6.22-rc4) and send me the result.
Now I see in the logs that there are also messages about the
report initialization failing, so we should also specify NOGET for this
device.
Could you please try the patch below in
On Fri, 2007-06-15 at 06:03 -0400, Daniel Hazelton wrote:
> In other words, it applies to *SECTIONS* of the code, not to individual
> object
> code files. This is why kernel modules can have their own, separate license
> from the kernel. It isn't until the code is shipped as a *standard* part of
On Friday 15 June 2007 06:18:59 David Greaves wrote:
> Daniel Hazelton wrote:
> >> Now for a different PoV:
> >> Do I think Tivoisation is bad for the community ?
> >> Of course I think it is but your mileage may vary.
> >
> > And I happen to agree with you. What I disagree with is taking steps to
On Sun, Jun 03, 2007 at 08:38:46PM +0200, Jörn Engel ([EMAIL PROTECTED]) wrote:
> This round the patch is split into file-sized hunks. There actually
> seem to be kernel developers not manly enough to digest 6000+ lines of
> code at once. An I thought I was the only wimp around.
>
> Again, anyon
On Friday 15 June 2007, Mikael Pettersson wrote:
> > --- linux-2.6.22-rc4-fixed/fs/quota.c.orig2007-06-14 15:55:26.0
> > +0400
> > +++ linux-2.6.22-rc4-fixed/fs/quota.c 2007-06-14 19:50:13.0 +0400
> ...
> > +#if defined(CONFIG_X86_64) || defined(CONFIG_IA64)
> > +/*
> > + * Thi
On Sun, Jun 03, 2007 at 08:44:29PM +0200, Jörn Engel ([EMAIL PROTECTED]) wrote:
> --- /dev/null 2007-03-13 19:15:28.862769062 +0100
> +++ linux-2.6.21logfs/fs/logfs/dir.c 2007-06-03 19:54:55.0 +0200
...
> +static int __logfs_dir_walk(struct inode *dir, struct dentry *dentry,
> +
You can find a half-year back discussions of this patch:
First attempt: http://lkml.org/lkml/2006/10/19/123
Second attempt: http://lkml.org/lkml/2006/10/25/57
I think they will answer your questions.
Thank you,
Vasily
On Fri, 2007-06-15 at 12:03 +0200, Mikael Pettersson wrote:
> On Fri, 15 Jun
On Friday 15 June 2007 06:02:11 Bernd Paysan wrote:
> On Friday 15 June 2007 07:24, Theodore Tso wrote:
> > On Thu, Jun 14, 2007 at 08:20:19PM -0300, Alexandre Oliva wrote:
> > > So, you see, your statement above, about wanting to be able to use
> > > other people's improvements, cannot be taken wi
On Fri, 15 Jun 2007, Pim Zandbergen wrote:
Justin Piszcz wrote:
That's strange, I guess different chipsets 'chew' up different amounts of
memory OR you have your DVT(?) (video-card memory/aperature) set to 256MB?
I have mine set to 128MB, in top:
Mem: 8039576k total, 6187304k used, 185
Hello
Randy Dunlap wrote:
> On Thu, 14 Jun 2007 03:40:56 +0300 Vladimir V. Saveliev wrote:
>
>> Hello
>>
>> Randy Dunlap wrote:
>>> while running fsx-linux on x86_64 system:
>>>
>> thanks, I will take a look.
>>
>> Is it reproducible? If yes, would you please try on some earlier kernel?
>
> I ra
Jesse Barnes wrote:
Thanks for testing, Pim. Glad it works for you.
The pleasure was all on my side.
Keep an eye out for BIOS upgrades, the next version might fix it.
What, are you going to report this to GigaByte?
Thanks,
Pim
-
To unsubscribe from this list: send the line "unsubscri
Nice three documents with many numbers:
http://blogs.sun.com/ontherecord/entry/now_available_three_new_solaris
kloczek
--
---
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
--
Daniel Hazelton wrote:
Now for a different PoV:
Do I think Tivoisation is bad for the community ?
Of course I think it is but your mileage may vary.
And I happen to agree with you. What I disagree with is taking steps to
make "bad == illegal". I also have a problem with doing things that force
Justin Piszcz wrote:
That's strange, I guess different chipsets 'chew' up different amounts
of memory OR you have your DVT(?) (video-card memory/aperature) set to
256MB? I have mine set to 128MB, in top:
Mem: 8039576k total, 6187304k used, 1852272k free, 696k buffers
Me:
Mem: 74166
On Thu, 14 Jun 2007, Jiri Kosina wrote:
> I have met such devices already, we are fixing their report descriptors
> on the fly before they enter the HID parser. I will prepare a patch for
> you to test (probably tomorrow, sorry).
Islam,
please try the patch below (against 2.6.22-rc4) and send
On Friday 15 June 2007 05:30:09 Bernd Paysan wrote:
> On Friday 15 June 2007 01:46, [EMAIL PROTECTED] wrote:
> > if you cannot modify the software that runs on your Tivo hardware you
> > haven't tried very hard.
>
> Yes, but the GPLv2 clearly says that you don't have to try very hard. The
> preferr
On Fri, 15 Jun 2007 13:01:48 +0400, Vasily Tarasov wrote:
> OpenVZ Linux kernel team has discovered the problem
> with 32bit quota tools working on 64bit architectures.
> In 2.6.10 kernel sys32_quotactl() function was replaced by sys_quotactl() with
> the comment "sys_quotactl seems to be 32/64bit
On Friday 15 June 2007 05:17:44 David Woodhouse wrote:
> On Fri, 2007-06-15 at 04:58 -0400, Daniel Hazelton wrote:
> > > If the module is distributed 'as a separate work', _then_ what you say
> > > is true: the only reason you'd have a right to the source is if the
> > > module is considered a 'der
>> > by your argument, the user has some "right to modify the
software", on
>> > that piece of hardware it bought which had free software on it,
correct?
>>
>> Yes. This means the hardware distributor who put the software in
>> there must not place roadblocks that impede the user to get where she
On Friday 15 June 2007 07:24, Theodore Tso wrote:
> On Thu, Jun 14, 2007 at 08:20:19PM -0300, Alexandre Oliva wrote:
> > So, you see, your statement above, about wanting to be able to use
> > other people's improvements, cannot be taken without qualification.
>
> No. Linus and other Linux kernels
From: Arnd Bergmann <[EMAIL PROTECTED]>
Date: Fri, 15 Jun 2007 11:31:37 +0200
> One common problem with 32 bit system call and ioctl emulation
> is the different alignment rules between i386 and 64 bit machines.
> A number of drivers work around this by marking the compat
> structures as 'attribut
Linus,
Please pull from the repository and branch at
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
to get a fix for a fairly critical bug which allows, under certain conditions,
guest fpu state to find its way into the host fpu.
Avi Kivity (1):
KVM: Prevent guest f
SCSI marks internal commands with REQ_PREEMPT and push it at the front
of the request queue using blk_execute_rq(). When entering suspended
or frozen state, SCSI devices are quiesced using
scsi_device_quiesce(). In quiesced state, only REQ_PREEMPT requests
are processed. This is how SCSI blocks
On Thursday 14 June 2007 22:47, David Schwartz wrote:
> The GPL does not require it to be easy in fact to modify the piece of
> software.
Yes it does, section 3: "The source code for a work means the preferred form
of the work for making modifications to it." It then even lists that you
need to
One common problem with 32 bit system call and ioctl emulation
is the different alignment rules between i386 and 64 bit machines.
A number of drivers work around this by marking the compat
structures as 'attribute((packed))', which is not the right
solution because it breaks all the non-x86 archite
On Friday 15 June 2007 01:46, [EMAIL PROTECTED] wrote:
> if you cannot modify the software that runs on your Tivo hardware you
> haven't tried very hard.
Yes, but the GPLv2 clearly says that you don't have to try very hard. The
preferred form of modification has to be distributed. I can run a
de
On Friday 15 June 2007, Benjamin Herrenschmidt wrote:
>
> > Only on i386. I think you just broke ppc32-on-ppc64.
>
> Indeed... I'm pretty sure the 64 bits quantity will be naturally aligned
> on ppc32 (and possibly others).
>
Ok, I'll bite. I've been telling people for ages what the right solut
On Thu, 2007-06-14 at 13:58 -0700, Ollie Wild wrote:
> A good heuristic, though, might be to limit
> argument size to a percentage (say 25%) of maximum stack size and
> validate this inside copy_strings().
This seems to do:
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
fs/exec.c |
Jared Hulbert wrote:
An alternative approach, which does not need to have struct page at
hand, would be to use the nopfn vm operations struct. That one would
have to rely on get_xip_pfn.
Of course! Okay now I'm begining to understand.
Sorry, but I think I was educated yesterday that ->fault() (
On Friday 15 June 2007 02:24:37 Michael Gerdau wrote:
> > Because GPLv2 doesn't enforce limitations on the hardware a GPL'd work
> > can be put on. It doesn't make artificial distinctions between
> > "Commercial", "Industrial" and "User". What it does is *ATTEMPT* to
> > ensure that nobody receivin
On 6/15/07, Bernd Petrovitsch <[EMAIL PROTECTED]> wrote:
Says the one without real name who is full quoting including even the
mailing list footers.
hmm. including footers was a mistake. sigh!
but i really dont understand why the real name is needed unless im
submitting some patches!
"What's
> 2) I don't know how the FSF is approaching the Linux developers, but
> what I've been personally trying to do in this infinite thread was
> mainly to set the record straight that v3 did not change the spirit of
> the license, like some have claimed.
The FSF have certainly tried to talk to me a b
On Fri, 2007-06-15 at 04:58 -0400, Daniel Hazelton wrote:
> > If the module is distributed 'as a separate work', _then_ what you say
> > is true: the only reason you'd have a right to the source is if the
> > module is considered a 'derivative work'.
> >
> > But when you distribute the same module
Cyrill wrote:
>> err = foo(arg_a, arg_b, arg_c,
>>arg_d);
1234
(note: monospace font needed)
Dave wrote:
> The Documentation/CodingStyle says:
>
> Outside of comments, documentation and except in Kconfig, spaces are never
> used for indentation, and the above
On Fri, 2007-06-15 at 10:50 +0200, Nicolas Ferre wrote:
> From: Nicolas Ferre <[EMAIL PROTECTED]>
>
> Fixes STN LCD support for the atmel_lcdfb framebuffer driver.
>
> Signed-off-by: Nicolas Ferre <[EMAIL PROTECTED]>
Acked-by: Jan Altenberg <[EMAIL PROTECTED]>
-
To unsubscribe from this list: s
On Fri, Jun 15, 2007 at 01:58:20PM +1000, Neil Brown wrote:
> Certainly. But the raid doesn't need to be tightly integrated
> into the filesystem to achieve this. The filesystem need only know
> the geometry of the RAID and when it comes to write, it tries to write
> full stripes at a time.
XFS
Luca wrote:
>>
>> Got it!
>> The emulator skips the writeback if the old value is unchanged, so the
>> apic doesn't see the write.
>>
>> Forcing the writeback:
>>
>> - if ((d & Mov) || (dst.orig_val != dst.val)) {
>> - if ((d & Mov) || (dst.orig_val != dst.val) || isxchg) {
>>
>> seems to
On Sun, Jun 03, 2007 at 08:46:04PM +0200, Jörn Engel ([EMAIL PROTECTED]) wrote:
> --- /dev/null 2007-03-13 19:15:28.862769062 +0100
> +++ linux-2.6.21logfs/fs/logfs/gc.c 2007-06-03 19:18:57.0 +0200
Number of bugs in case of error looks quite sad...
--
Evgeniy Polyakov
-
To unsu
On Fri, 2007-06-15 at 12:17 +0530, debian developer wrote:
[...]
> And *Please* do not top-post!
Says the one without real name who is full quoting including even the
mailing list footers.
SCNR,
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156
> > A Tivo box is a collection of literary works protected by copyright,
> > designs protected by design patents and copyright, names and logos
> > protected by trademarks, functionalities protected by patents and many
> > more things. These are the things that restrict what I may do with it
>
From: Nicolas Ferre <[EMAIL PROTECTED]>
Adds STN LCD support on at91sam9261ek. Uses a black and
white screen from Hitachi : SP06Q002.
Signed-off-by: Nicolas Ferre <[EMAIL PROTECTED]>
---
Submitted in linux-fbdev for a RFC but will make its way
through the AT91 maintainer.
Relies on the CONF
On Thu, Jun 14, 2007 at 07:23:40PM -0700, Andrew Morton wrote:
> On Thu, 14 Jun 2007 19:04:27 -0700 (PDT) Christoph Lameter <[EMAIL
> PROTECTED]> wrote:
> > > > Of course there is. The seeks are reduced since there are an factor
> > > > of 16 less metadata blocks. fsck does not read files. It jus
On Jun 14 2007 18:32, Matthias Schniedermeyer wrote:
> markus reichelt wrote:
>
>> PS: Just wondering: Who came up with this "on-demand" hype?
>
> I don't remember the names, but i remember the root causes. Here we go:
http://lkml.org/lkml/2007/3/22/86
Jan
--
-
To unsubscribe from thi
501 - 600 of 635 matches
Mail list logo
