On Tue, 1 May 2007, Mel Gorman wrote:
>anti-fragmentation-switch-over-to-pfn_valid_within.patch
>
> These patches are the grouping pages by mobility patches. They get tested
> every time someone boots the machine from the perspective that they affect
> the page allocator. It is working to kee
On Tuesday 01 May 2007, Frank van Maarseveen wrote:
>Tested on 2.6.20.6 and 2.6.21.1
>
>I decided to swich from the old IDE drivers to libata and now there
>seems to be a little but annoying problem: cannot mount an ISO image
>after burning it.
>
>May 1 14:32:55 kernel: attempt to access beyond en
On Tue, May 01, 2007 at 07:42:29AM -0700, Trond Myklebust wrote:
> On Thu, 2007-04-26 at 15:13 -0400, Jeff Layton wrote:
> > I recently posted this patch to the nfs mailing list, but got no comment.
> > Reposting with an actual "[PATCH]" subject...
> >
> > In certain situations, a NFSv4 client can
Hi,
On Thu, Jan 18, 2007 at 11:16:51PM +, Pavel Machek wrote:
> Hi!
>
> > > > Especially the PCI video_state trick finally got me a working resume on
> > > > 2.6.19-ck2 r128 Rage Mobility M4 AGP *WITH*(!) fully enabled and working
> > > > (and keeping working!) DRI (3D).
> > >
> > > Can we g
On Tue, 2007-05-01 at 15:42 +1000, Nigel Cunningham wrote:
> Hi.
>
> Does anyone have VMware working on x86_64 with 2.6.21? It's working fine
> for me with 2.6.20, but freezes the whole computer with 2.6.21. Before I
> start a git-bisect, I thought I might ask if anyone knew of some
> compilation
Milton Miller wrote:
In commit d52df4a35af569071fda3f4eb08e47cc7023f094, the description
talks about emulating another driver by setting addtional bits and
the being unable to test when submitted. Seeing the & operator to
set more bits made me suspicious, and indeed the bits are defined
in posit
Hi Markus,
Em Seg, 2007-04-30 às 23:17 +0200, Markus Rechberger escreveu:
> Hi,
>
> Trent Piepho wrote another patch for it, it just completes Uwe's patch
> in the end.
>
> http://linuxtv.org/hg/~tap/dst-new?cmd=changeset;node=bbdd2b53cd5c;style=gitweb
The above patch plus the other on
http://l
at the risk of spawning yet another thread and another flamefest,
what *are* the kernel features that should be considered candidates
for removal, either now or at some point in the future.
please, no discussions about mechanisms or kernel warnings or the
like -- just the features whose value
On Tue, 2007-05-01 at 17:36 +0300, Paul Sokolovsky wrote:
> Either way, I don't pledge to be a HW designer with
> contemporary lexicon. The aim was simple - as a single word would be
> too ambiguous, general, or vice-versa, omitting, then acronym is
> needed, hopefully existing, and not new
Antonino A. Daplas wrote:
>
> And this will entail a lot of work to change (Is it worth it to rework
> the code and remove the limitation?). The linux-console project
> (http://linuxconsole.sourceforge.net/) might have , but I don't know its
> current status.
>
Well, I think the consensus is tha
> > if (veryverylengthycondition1 &&
> > smallcond2 &&
> > (conditionnumber3a ||
> > condition3b)) {
> > ...
> > }
>
> It's horrid. I'd much rather see
>
> if (veryverylengthycondition1 &&
> smallcond2 &&
>
On Tue, 2007-05-01 at 08:05 -0700, Randy Dunlap wrote:
> I prefer this format also, but I'm not sure that we can get it
> into CodingStyle. CodingStyle is about (either) concensus or
> dictum, but I don't see us close to concensus...
CodingStyle is mostly about consensus. We don't have a consens
Allow selection of the compression mode for jffs2 via a sysfs
attribute. This establishes a sysfs presence for jffs2 through
which other compression options could easily be exported too.
Signed-off-by: Richard Purdie <[EMAIL PROTECTED]>
---
fs/Kconfig |9
fs/jffs2/compr.c | 4
The following patch series adds LZO compression support to the kernel
and exposes it in a variety of places (jffs2, crypto).
Its a resend of a previous posted series, rediffed against recent
kernels with the couple of minors issues raised by David Woodhouse
addressed.
This patch series is also av
On Tue, 1 May 2007, David Woodhouse wrote:
> On Tue, 2007-05-01 at 11:00 +0200, Geert Uytterhoeven wrote:
> >
> > if (veryverylengthycondition1 &&
> > smallcond2 &&
> > (conditionnumber3a ||
> > condition3b)) {
> > ...
> > }
>
>
Add LZO1X compression/decompression support to jffs2.
LZO's interface doesn't entirely match that required by jffs2 so a
buffer and memcpy is unavoidable.
Signed-off-by: Richard Purdie <[EMAIL PROTECTED]>
---
fs/Kconfig| 10
fs/jffs2/Makefile |1 +
fs/jffs2/compr.c
On Tue, 01 May 2007 15:16:13 +0100 David Woodhouse wrote:
> On Tue, 2007-05-01 at 11:00 +0200, Geert Uytterhoeven wrote:
> >
> > if (veryverylengthycondition1 &&
> > smallcond2 &&
> > (conditionnumber3a ||
> > condition3b)) {
> > ...
>
Add LZO1X compression/decompression support to the kernel.
This is based on the standard userspace lzo library, particularly
minilzo with the headers much trimmed down and simplified for kernel
use. Its structured so that it should still diff with the userspace
version for ease of future updating
Hi.
On Tue, 2007-05-01 at 09:46 -0400, Mark Lord wrote:
> Nigel Cunningham wrote:
> ..
> > Yeah. It turns out that I was still on WS 6 beta 1. Upgrading to beta 2
> > made the problem go away.
>
> Then you're still behind. They've had a WS6 RC available for the past week.
Or I'm confused about
Add a "favourlzo" compression mode to jffs2 which tries to
optimise by size but gives lzo an advantage when comparing sizes.
This means the faster lzo algorithm can be preferred when there
isn't much difference in compressed size (the exact threshold can
be changed).
Signed-off-by: Richard Purdie
Bill Irwin wrote:
> This patch introduces CONFIG_DEBUG_STACK, which vmalloc()'s task and IRQ
> stacks in order to establish guard pages. In such a manner any stack
> overflow that references pages immediately adjacent to the stack is
> immediately trapped with a fault, which precludes silent memory
On Tue, 2007-05-01 at 17:07 +0200, Geert Uytterhoeven wrote:
> For clarity, if it fits, I prefer that one, too.
I don't think that was under question, was it?
My point was that I prefer it even when it _doesn't_ fit.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
crypto: Add LZO compression support to the crypto interface
Add LZO1X compression support to the crypto interface, including
a couple of tests.
Also convert test_deflate into a more generic test_compress() and
avoid duplicating the data for compression and decompression tests
since this can alway
Hi Arjan.
On Tue, 2007-05-01 at 07:57 -0700, Arjan van de Ven wrote:
> On Tue, 2007-05-01 at 15:42 +1000, Nigel Cunningham wrote:
> > Hi.
> >
> > Does anyone have VMware working on x86_64 with 2.6.21? It's working fine
> > for me with 2.6.20, but freezes the whole computer with 2.6.21. Before I
>
| linux/net/rxrpc/af_rxrpc.c: In function 'rxrpc_kernel_begin_call':
| linux/net/rxrpc/af_rxrpc.c:303: error: dereferencing pointer to incomplete
type
| linux/net/rxrpc/af_rxrpc.c: In function 'af_rxrpc_init':
| linux/net/rxrpc/af_rxrpc.c:820: warning: implicit declaration of function
'register_
On Tue, 2007-05-01 at 13:17 +0100, James Pearson wrote:
> Antonino A. Daplas wrote:
> > On Mon, 2007-04-30 at 13:58 +0100, James Pearson wrote:
> >
> >>Antonino A. Daplas wrote:
> >>
> >>>On Fri, 2007-04-27 at 18:08 +0100, James Pearson wrote:
> It does indeed seem that the switching back and for
Milton Miller wrote:
In commit d52df4a35af569071fda3f4eb08e47cc7023f094, the description
talks about emulating another driver by setting addtional bits and
the being unable to test when submitted. Seeing the & operator to
set more bits made me suspicious, and indeed the bits are defined
in posit
On Tue, 2007-05-01 at 10:13 -0400, Mark Lord wrote:
> Thomas Gleixner wrote:
> > On Tue, 2007-05-01 at 09:34 -0400, Mark Lord wrote:
> >>> now at 3232363876949 nsecs
> >> ...
> >>
> >> Oh, in case it matters any:
> >> that /proc/timer_list is from the system with CFS-V7 also patched in.
> >
> > It
Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git for-linus
to receive the following updates:
drivers/misc/tifm_7xx1.c | 332 +++
drivers/misc/tifm_core.c | 305 +++--
drivers/mmc/Kconfig |
Hi RAM,
The following result was the effect of "info threads"
command
Since this is GDB bug that you are reporting, please could you either
send it to the GDB mailing list at <[EMAIL PROTECTED]> or else fill in
a bug report at:
http://sourceware.org/gdb/bugs/
Thank you.
Nick
-
To unsub
Robert P. J. Day wrote:
at the risk of spawning yet another thread and another flamefest,
what *are* the kernel features that should be considered candidates
for removal, either now or at some point in the future.
please, no discussions about mechanisms or kernel warnings or the
like -- just
Hello, Alan.
Alan Cox wrote:
> If you have a controller with one channel disabled and unmapped the new
> iomap code blindly tries to iomap unconfigured BARs. Later on the code
> does the right thing and checks for unmapped bars but it is done in the
> wrong order
>
> Reorder the checks and make t
Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> Should AF_RXRPC depend on KEYS?
Ummm... yes it probably should. It's just that I normally build rxkad too,
and that does depend on keys.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
Michel Lespinasse wrote:
>
> I'm having an issue with lost ticks, runnign linux 2.6.20.10 on an
> intel DQ965GF motherboard. For some reason this occurs with clock-like
> regularity, always exactly 24 lost ticks, about every two seconds.
> This is running with 250-HZ ticks, and the small pause eve
On Fri, 27 Apr 2007, Linux Kernel Mailing List wrote:
> [AF_RXRPC]: Make the in-kernel AFS filesystem use AF_RXRPC.
>
> Make the in-kernel AFS filesystem use AF_RXRPC instead of the old RxRPC
> code.
> --- a/fs/afs/fsclient.c
> +++ b/fs/afs/fsclient.c
> + if (call->count
Andi Kleen wrote:
> vfat implements compat handlers for these ioctls, but when they
> were executed on other file systems the kernel would still complain
> about an unknown compat ioctl. Just declare them as compatible
> and let them be rejected when not needed by the normal path.
>
> This makes
On 5/1/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Antonino A. Daplas wrote:
>
> And this will entail a lot of work to change (Is it worth it to rework
> the code and remove the limitation?). The linux-console project
> (http://linuxconsole.sourceforge.net/) might have , but I don't know its
>
Jay Cliburn wrote:
Please accept the following trivial patches to the atl1 driver.
- use dev_printk macros
- fix whitespace damage
Acked-By: Chris Snook <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
M
Bill Irwin a écrit :
On Tue, May 01, 2007 at 06:26:23AM +0200, Eric Dumazet wrote:
Hum... We lose a usefull 2G/2G split. Should'nt we use a patch to change
PAGE_OFFSET to 0x800 instead of 0x7800 and keep 2G/2G split ?
On Tue, May 01, 2007 at 08:21:32AM +0200, Andi Kleen wrote:
I dropp
net/rxrpc/af-rxrpc.ko needs csum_partial_copy_from_user
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
---
arch/m68k/lib/checksum.c |3 +++
1 file changed, 3 insertions(+)
--- linux-m68k-2.6.21.orig/arch/m68k/lib/checksum.c
+++ linux-m68k-2.6.21/arch/m68k/lib/checksum.c
@@ -320,6 +320
>> > Hi,
>> Hi
>> > the new longhaul driver of 2.6.21 is broken on my Via Eden board.
>> > Frequencies can no longer be switched by whatever governor.
>> > [...]
>> >
>> > I ported the longhaul driver from 2.6.20.7 to 2.6.21, it works fine.
>> Yes. My fault. Bug is known, but it was to late to incl
Antonino A. Daplas wrote:
On Tue, 2007-05-01 at 13:17 +0100, James Pearson wrote:
Antonino A. Daplas wrote:
On Mon, 2007-04-30 at 13:58 +0100, James Pearson wrote:
Antonino A. Daplas wrote:
On Fri, 2007-04-27 at 18:08 +0100, James Pearson wrote:
It does indeed seem that the switching
Jan Engelhardt wrote:
> Change Kconfig objects from "menu, config" into "menuconfig" so
> that the user can disable the whole feature without having to
> enter the menu first.
>
> Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
>
As promised, an updated patch.
--
-- Pierre Ossman
Li
On Tue, 2007-05-01 at 17:53 +0400, Dmitry Krivoschekov wrote:
> Hi Paul,
> I think your referring to the term "SoC (system-on-chip)" is confusing
> (at least for me). You rather consider companion chips than SoCs.
A 'System' does not imply a CPU. A 'Computer System' would but the word
system itse
On Tue, 2007-05-01 at 10:13 -0400, Mark Lord wrote:
> Of possible interest is that the bottom of the 25line screen capture
> differs somewhat from the 50line capture.. see for yourself.
> This is 100% consistent from boot to boot.
>
> Using CONFIG_DETECT_SOFTLOCKUP=y eliminates the problem,
> so t
Wolfgang Erig wrote:
> Sorry
> for detecting this 2 year old regression so late.
>
> 2.6.13 or later is bad.
> 2.6.12 is good,
>
> "git bisect" worked fine and points to the attached patch.
> The patch is pretty small. The problem seemed to be dependant
> on the PCI-architecture of these particul
Jon Burgess wrote:
> It appears the problem is that the driver is using streamed PCI and
> needs to explicitly sync the data otherwise it breaks when the SWIOTLB
> is in use. A call to pci_unmap_sg() was missing too.
>
> This patch is against the current v4l-dvb HG tree.
>
> I've only tested the
On Tue, 01 May 2007 12:40:22 +0300 Thomas Backlund wrote:
> arg, attachment. :(
[parts of patch copy/pasted here for comments]
+static int pirq_pico_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
+{
+ outb(0x10+((pirq-1)>>1), 0x24);
+ return ((pirq-1)&1) ? (inb(0x26)>>4
On Mon, 30 Apr 2007 22:38:59 -0700 Andrew Morton wrote:
> On Tue, 1 May 2007 08:24:56 +0200 Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > > The bug is in firstfloor only, and the fix (if present) will be there too.
> > >
> > >
> > >
> > > Nope,
> > >
> > > ftp://ftp.firstfloor.org/pub/ak/x86_64
John Anthony Kazos Jr. <[EMAIL PROTECTED]> wrote:
> if (veryverylengthycondition1
> && smallcond2
> && (conditionnumber3a
> || condition3b)) {
> ...
> }
>
> Clear, crisp, and 80-wide. I also like how the logical operator
Greg KH wrote:
> On Mon, Apr 30, 2007 at 08:45:25PM -0400, Jeff Garzik wrote:
>> Chris Wright wrote:
>>> 2) you can add them
>>> runtime in userspace (and for pcmcia too after patch in question is
>>> applied), so we've historically avoided that kind of patch for -stable.
>>
>> Due to distro instal
Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> This causes a compile failure on m68k:
Hmmm... I couldn't actually test m68k as I couldn't get it to compile. Can
you give me a good config I can use as a base?
> | linux/fs/afs/fsclient.c: In function 'afs_deliver_fs_fetch_data':
> | linux/fs/afs
On Tue, May 01, 2007 at 09:17:14PM +0800, Xu CanHao wrote:
> Reiser4 may lack some core function, but ZFS on Solaris is as
> functional as ext3 on Linux(or even more). So compare Reiser4 with
> ZFS may be inappropriate.
Functional, but it's a new filesystem with not as much time-tested
experience
On Tue, 1 May 2007 08:22:58 +0200 Andi Kleen wrote:
> On Mon, Apr 30, 2007 at 10:16:24PM -0700, Randy Dunlap wrote:
> > On Tue, 1 May 2007 05:43:30 +0200 Andi Kleen wrote:
> >
> > > > Andi: unprocessor x86_64 running rc7-mm2 is hanging early in boot at
> > > > randomish times (presumably in the t
On Tue, 1 May 2007, Geert Uytterhoeven wrote:
>
> This causes a compile failure on m68k:
>
> | linux/fs/afs/fsclient.c: In function 'afs_deliver_fs_fetch_data':
> | linux/fs/afs/fsclient.c:269: warning: dereferencing 'void *' pointer
> | linux/fs/afs/fsclient.c:269: error: request for member 'v
From: On Behalf Of Satyam Sharma
> readable and obvious at first glance itself. For example, consider:
^^^
>
> if (veryverylengthycondition1 &&
> smallcond2 &&
> (conditionnumber3a ||
> condition3b)) {
>
Paul Sokolovsky wrote:
> Hello Dmitry,
>
> Tuesday, May 1, 2007, 4:53:09 PM, you wrote:
>
>> I think your referring to the term "SoC (system-on-chip)" is confusing
>> (at least for me). You rather consider companion chips than SoCs.
>
>> Yes, any chip integrating a number of controllers could be co
On Tue, 1 May 2007, David Howells wrote:
> Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> > This causes a compile failure on m68k:
>
> Hmmm... I couldn't actually test m68k as I couldn't get it to compile. Can
> you give me a good config I can use as a base?
>
> > | linux/fs/afs/fsclient.c: In
Thomas Gleixner wrote:
I meant disable HPET via: hpet=disable on the commandline
Screenshots for that are available here: http://rtr.ca/hrtimers/
hpet=disable fails, without the "switched to high resolution timer" message(s).
New snapshot of it now at the link above.
I also applied Tejun
Bill Irwin wrote:
>> This patch introduces CONFIG_DEBUG_STACK, which vmalloc()'s task and IRQ
>> stacks in order to establish guard pages. In such a manner any stack
>> overflow that references pages immediately adjacent to the stack is
>> immediately trapped with a fault, which precludes silent me
On Tue, 01 May 2007 17:30:36 +0200, Andre Tomt said:
> Robert P. J. Day wrote:
> > http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed
> Already documented in the kernel tarball, see
> Documentation/feature-removal-schedule.txt
Robert's point is that the file you cited is horrendously out
ian wrote:
> On Tue, 2007-05-01 at 17:53 +0400, Dmitry Krivoschekov wrote:
>> Hi Paul,
>
>> I think your referring to the term "SoC (system-on-chip)" is confusing
>> (at least for me). You rather consider companion chips than SoCs.
>
> A 'System' does not imply a CPU. A 'Computer System' would but
> > But distros can easily add the device id to their kernel if needed, it
> > isn't something that the -stable tree shoud be accepting. Otherwise, we
> > will be swamped with those types of patches...
> >
>
> Oh sure, leave the distros swamped with them instead. :)
>
> And they all have to do
Original-Nachricht
Datum: Tue, 01 May 2007 11:55:33 -0300
Von: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
An: Markus Rechberger <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], linux-kernel@vger.kernel.org, Manu Abraham <[EMAIL
PROTECTED]>
Betreff: [linux-dvb] Re: DST/BT878 module cust
Bill Irwin wrote:
>
> It's a shame that the resource scalability implications of vmallocspace
> allocations prevent this from being useful in production. One could, in
> principle, establish guard pages within ZONE_NORMAL, but for 4KB stacks
> it's somewhat awkward to dredge up 3 contigous pages,
On Tue, 2007-05-01 at 12:31 -0400, Mark Lord wrote:
> Thomas Gleixner wrote:
> >
> > I meant disable HPET via: hpet=disable on the commandline
> >
> >> Screenshots for that are available here: http://rtr.ca/hrtimers/
>
> hpet=disable fails, without the "switched to high resolution timer"
> m
Bill Irwin wrote:
>> It's a shame that the resource scalability implications of vmallocspace
>> allocations prevent this from being useful in production. One could, in
>> principle, establish guard pages within ZONE_NORMAL, but for 4KB stacks
>> it's somewhat awkward to dredge up 3 contigous pages,
Thomas Gleixner wrote:
On Tue, 2007-05-01 at 10:13 -0400, Mark Lord wrote:
Of possible interest is that the bottom of the 25line screen capture
differs somewhat from the 50line capture.. see for yourself.
This is 100% consistent from boot to boot.
Using CONFIG_DETECT_SOFTLOCKUP=y eliminates the
On Monday, April 30, 2007, Olivier Galibert wrote:
> On Sun, Apr 29, 2007 at 08:14:37PM -0600, Robert Hancock wrote:
> > -Validate that the area is reserved even if we read it from the
> > chipset directly and not from the MCFG table. This catches the case
> > where the BIOS didn't set the location
On Mon, 2007-04-30 at 16:20 -0700, Andrew Morton wrote:
[snip]
> Mel's moveable-zone work.
>
> I don't believe that this has had sufficient review and I'm sure that it
> hasn't had sufficient third-party testing. Most of the approbations thus far
> have consisted of people liking the overall idea
Hi folks,
I've looked around, but haven't been able to find any mbox-format
archives of linux-kernel. Does anything like that exist? It would be
really useful to me right now, just because of some network
connectivity problems I'm in the midst of. Downloading mbox files
looks like my best shot at
Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> On architectures that #define WANT_PAGE_VIRTUAL (frv/m68k/mips/extensa),
> page_address(page) expands to (page)->virtual, which fails if page is a
> void *.
On FRV, kmap_atomic() should always be an inline function (I wrote it:-):
static in
On Tue, May 01, 2007 at 12:14:11PM +1000, Neil Brown wrote:
> On Saturday April 21, [EMAIL PROTECTED] wrote:
> > When the kernel calls svc_reserve to downsize the expected size of an RPC
> > reply, it fails to account for the possibility of a checksum at the end of
> > the packet. If a client mount
Bill Irwin a écrit :
>> as a stopgap measure, but I'm not all that interested in grabbing patch
>> credits where others could do it easily enough. Either of the config
>> alterations is fine by me as they now stand; maybe Eric Dumazet might
>> care to do something like my suggestion at some point.
Hi Robert,
Em Sáb, 2007-04-28 às 06:32 -0400, Robert P. J. Day escreveu:
> Replace the call to MINOR() with a call to the inline iminor()
> routine.
>
> Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
>
> ---
>
> that's the last of those changes, but it's not clear who the official
> mainta
This basically gets voyager compiling, working and ship shape again. The
only change to code outside of voyager is a clockevents fix that has
been ack'd by Thomas Gleixner. The patch is available here:
master.kernel.org:/pub/scm/linux/kernel/git/jejb/voyager-2.6.git
The short changelog is:
Chris
2007/5/2, Theodore Tso <[EMAIL PROTECTED]>:
On Tue, May 01, 2007 at 09:17:14PM +0800, Xu CanHao wrote:
> Reiser4 may lack some core function, but ZFS on Solaris is as
> functional as ext3 on Linux(or even more). So compare Reiser4 with
> ZFS may be inappropriate.
Functional, but it's a new files
Hi,
On 01/05/07, Zack Brown <[EMAIL PROTECTED]> wrote:
Hi folks,
I've looked around, but haven't been able to find any mbox-format
archives of linux-kernel. Does anything like that exist? It would be
really useful to me right now, just because of some network
connectivity problems I'm in the mi
This patch adds support for PicoPower PT86C523 IRQ router to be used
with the in-kernel yenta driver for CardBus.
With this patch cardbus works on e.g. Dell Latitude XPi P150CD.
Initial patch for kernel 2.4 series by Sune Mølgaard
http://molgaard.org/code/linux-2.4.31-picopower.patch
Ported
> +static void * __init __alloc_irqstack(int cpu)
> +{
> + if (!cpu)
> + return __alloc_bootmem(THREAD_SIZE, THREAD_SIZE,
> + __pa(MAX_DMA_ADDRESS));
> +
> + return (void *)__get_free_pages(GFP_KERNEL,
> +
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
>
> BTW, the PSF font format documentation seems to suggest that
> there is a way to make the kernel handle combining accents:
> http://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html
> Does anybody know if that really works? I coul
Thomas Backlund wrote:
Sorry, I don't see any changes. Did you send the wrong patch file?
This patch adds support for PicoPower PT86C523 IRQ router to be used
with the in-kernel yenta driver for CardBus.
With this
On Tue, May 01, 2007 at 01:01:27PM -0400, Jeff Layton wrote:
> On Tue, May 01, 2007 at 12:14:11PM +1000, Neil Brown wrote:
> >
> > Yes, that asn1 encoding does seem rather awkward.
> >
> > Maybe we should just use RPC_MAX_AUTH_SIZE like other bits of GSS code
> > does. There is no great cost in
Hi Andi,
On 01 May 2007 14:19:45 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote:
Also have the cache performance concerns raised on the original review
been addressed?
I am only aware of the fget_light() related issues Eric Dumazet raised
but it's fixed. If you're thinking of something else, coul
dvb-core is not started early enough when device drivers that use dvb are
compiled in so device_register_device fails (silently) since dvb_class is
NULL, this runs dvb_init using subsys_initclass instead of module_init.
dvb_register_device will now check the return value of class_device_create.
Hello Dmitry,
Tuesday, May 1, 2007, 7:38:44 PM, you wrote:
> ian wrote:
>> On Tue, 2007-05-01 at 17:53 +0400, Dmitry Krivoschekov wrote:
>>> Hi Paul,
>>
>>> I think your referring to the term "SoC (system-on-chip)" is confusing
>>> (at least for me). You rather consider companion chips than SoCs.
On 01/05/07 18:12, Simon Arlott wrote:
dvb_class is NULL, this runs dvb_init using subsys_initclass instead of
module_init.
That should of course be subsystem_initCALL not "initclass".
--
Simon Arlott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
Randy Dunlap skrev:
Thomas Backlund wrote:
Sorry, I don't see any changes. Did you send the wrong patch file?
Yep :-(
Here is the correct one:
This patch adds support for PicoPower PT86C523 IRQ router to be used
with the in-kernel yenta driver for CardBus.
With this patch cardbus work
Bill Irwin <[EMAIL PROTECTED]> writes:
>
> Only 1GB-aligned kernel/user splits are now handled for PAE. The
> 2GB/2GB split attempts to avoid aliasing vmallocspace with the 1:1
> mapping for physical memory by using an actual split of 1.875/2.125
> to accommodate 128MB of vmallocspace out of what
Hello Richard,
Tuesday, May 1, 2007, 6:01:15 PM, you wrote:
> On Tue, 2007-05-01 at 17:36 +0300, Paul Sokolovsky wrote:
>> Either way, I don't pledge to be a HW designer with
>> contemporary lexicon. The aim was simple - as a single word would be
>> too ambiguous, general, or vice-versa,
On May 1 2007 11:01, Robert P. J. Day wrote:
>
> at the risk of spawning yet another thread and another flamefest,
>what *are* the kernel features that should be considered candidates
>for removal, either now or at some point in the future.
>
> please, no discussions about mechanisms or kernel w
On Tue, May 01, 2007 at 03:40:36PM +0200, Tejun Heo wrote:
> >> Tejun, don't we have a fallback for when IDENTIFY fails?
> >> If the drive rejects it (err=0x04), then this can mean only one thing:
> >> unsupported command, so we next must try PACKET_IDENTIFY.
>
> Up until now, we've been depending
On Mon, 30 Apr 2007, Andrew Morton wrote:
> ...
> mm-detach_vmas_to_be_unmapped-fix.patch
> ...
> Misc MM things. Will merge.
No, I think that one is just drifting like flotsam towards mainline,
because nobody at all has yet found time to look at it. And Mr Akuster
appears not to have signed of
On Tue, 1 May 2007 09:22:33 -0700 Randy Dunlap wrote:
> On Tue, 1 May 2007 08:22:58 +0200 Andi Kleen wrote:
>
> > On Mon, Apr 30, 2007 at 10:16:24PM -0700, Randy Dunlap wrote:
> > > On Tue, 1 May 2007 05:43:30 +0200 Andi Kleen wrote:
> > >
> > > > > Andi: unprocessor x86_64 running rc7-mm2 is ha
On Fri, Apr 27, 2007 at 11:06:47AM -0400, Jeff Dike wrote:
> On Thu, Apr 26, 2007 at 09:58:25PM -0700, Valerie Henson wrote:
> > Here's an example, spelled out:
> >
> > Allocate file 1 in chunk A.
> > Grow file 1.
> > Chunk A fills up.
> > Allocate continuation inode for file 1 in chunk B.
> > Chu
On Mon, Apr 09, 2007 at 04:53:15PM -0700, Andrew Morton wrote:
>> Seems sane. Could we please get it tested and get a full description in
>> place? Something which provides enough detail for the manpage maintainers.
>> Also, a quick comparison between Linux's RUSAGE_THREAD and $other-os's
>> impl
At some point in the past, I wrote:
>> +static void * __init __alloc_irqstack(int cpu)
>> +{
>> +if (!cpu)
>> +return __alloc_bootmem(THREAD_SIZE, THREAD_SIZE,
>> +__pa(MAX_DMA_ADDRESS));
>> +
>> +return (void *)__get_free_pages(GFP_KE
what also puzzles me... almost every filesystem that's not at revision 1
anymore (ext2/3/4, reiser4, smb2) does not have the usually omnipresent "fs"
suffix anymore (cf. reiserfs, smbfs).
Maybe it's time to drop all the "fs" suffixes? :)
For the case of cifs (and nfs and afs) the "fs" is part
[EMAIL PROTECTED] wrote:
This patch adds the main containers framework - the container
filesystem, and the basic structures for tracking membership and
associating subsystem state objects to tasks.
[snip]
+*** notify_on_release is disabled in the current patch set. It may be
+*** reactivated
On 5/1/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> This patch adds the main containers framework - the container
> filesystem, and the basic structures for tracking membership and
> associating subsystem state objects to tasks.
[snip]
> +*** notify_on_release is disab
201 - 300 of 668 matches
Mail list logo
