On Wed, Mar 02, 2005 at 02:00:30PM -0800, Philippe Troin wrote:
> + /* Asus K8V Se Deluxe bugfix. Correct VPD content */
> + /* MBo April 2004 */
> + if( ((unsigned char)pAC->vpd.vpd_buf[0x3f] == 0x38) &&
> + ((unsigned char)pAC->vpd.vpd_buf[0x40] == 0x3c) &&
> + ((un
David S. Miller wrote:
On Wed, 02 Mar 2005 23:46:22 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
If Linus/DaveM really don't like -pre/-rc naming, I think 2.6.x.y is
preferable to even/odd.
All of these arguments are circular. If people think that even/odd
will devalue odd releases, guess what
Benjamin Herrenschmidt wrote:
On Fri, 2005-03-04 at 04:19 +1100, Nick Piggin wrote:
You don't want to do that for all architectures, as I said earlier.
eg. i386 can concurrently set the dirty bit with the MMU (which won't
honour the lock).
So you then need an atomic lock, atomic pte operations, an
Added a few patches, updated for 2.6.11 release.
NOTE: BK users -must- reclone netdev-2.6. Do not pull.
See attached for BK info, patch URL, and changelog.
BK users:
bk pull bk://gkernel.bkbits.net/netdev-2.6
or
bk pull bk://kernel.bkbits.net/jgarzik/netdev-2.6
P
Hi Hugh,
How about map an unmap each pte?
I mean remove the pte++ and use pte_offset_map for each incremented
address and then pte_unmap. So each incremented address is an index to
get the next pte via pte_offset_map.
BR,
Mauricio Lin.
On Wed, 2 Mar 2005 19:07:15 + (GMT), Hugh Dickins <[EM
On Wed, 2 Mar 2005 13:26:18 -0800 (PST), Joshua Hudson
<[EMAIL PROTECTED]> wrote:
> No obvous reason. Works fine with kernel 2.6.10
Does it work with i8042.noacpi kernel boot parameter?
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
On Thu, Mar 03, 2005 at 11:40:27AM +0530, Amol wrote:
> Hi,
> For an embedded developers perspective, Is there any other advantage of
> using initramfs over initrd apart from RAMFS benefits over RAMDISK ?
The fact that both are cumulable is very handy. Basically, you put all
the common tools and
Jeffrey Mahoney <[EMAIL PROTECTED]> wrote:
>
> This patch converts the usage of struct of_match to struct of_device_id,
> similar to pci_device_id. This allows a device table to be generated, which
> can be parsed by depmod(8) to generate a map file for module loading.
It breaks the power4 buil
Miguelanxo Otero Salgueiro <[EMAIL PROTECTED]> wrote:
>
> I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine
> (with kernel preemption activated).
> Doing a make oldconfig bring some new options. I selected the default
> value (for my system) for them, so I keep configuri
Hello, Jens.
Jens Axboe wrote:
On Thu, Mar 03 2005, Tejun Heo wrote:
Hello, Bartlomiej.
This patch fixes ide_dma_intr() oops which occurs for TASKFILE ioctl
using DMA dataphses. This is against the latest ide-dev-2.6 tree +
all your recent 9 patches.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
I
> And the reason it does _not_ work is that all the people we
> want testing sure as _hell_ won't be testing -rc versions.
At least they still test "real" releases..
So instead of making sure rc is really "release-candidate", we want to trick
people to test -pre as "real release", soon people wi
> > Do you have any objections to merging FUSE in mainline kernel?
> >
> > It's been in -mm for the 2.6.11 cycle, and the same code was released
> > a month ago as FUSE-2.2. So it should have received a fair amount of
> > testing, with no problems found so far.
> >
> > The one originally merged
On Wed, 2 Mar 2005, Andrew Morton wrote:
> > Any mmap changes requires the mmapsem.
>
> sys_remap_file_pages() will call install_page() under down_read(mmap_sem).
> It relies upon page_table_lock for pte atomicity.
This is not relevant since it only deals with file pages. ptes are only
installed
On Wed, 2005-03-02 at 21:51 -0800, Christoph Lameter wrote:
> On Wed, 2 Mar 2005, David S. Miller wrote:
>
> > Actually, I guess I could do the pte_cmpxchg() stuff, but only if it's
> > used to "add" access. If the TLB miss handler races, we just go into
> > the handle_mm_fault() path unnecessari
On Wed, Mar 02, 2005 at 05:15:36PM -0800, Linus Torvalds wrote:
> On Wed, 2 Mar 2005, Greg KH wrote:
> > I do understand what you are trying to achieve here, people don't really
> > test the -rc releases as much as a "real" 2.6.11 release. Getting a
> > week of testing and bugfix only type patches
On Thu, Mar 03 2005, Tejun Heo wrote:
> Hello, Bartlomiej.
>
> This patch fixes ide_dma_intr() oops which occurs for TASKFILE ioctl
> using DMA dataphses. This is against the latest ide-dev-2.6 tree +
> all your recent 9 patches.
>
> Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
>
> Index: li
On Wed, Mar 02, 2005 at 01:18:17PM -0800, Andrew Morton wrote:
> Jeff Garzik <[EMAIL PROTECTED]> wrote:
> >
> > > Thing is, CRYPTO_AES on only selectable on x86.
> >
> > You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
> > the dependencies are a bit weird:
> >
> > config
David Howells <[EMAIL PROTECTED]> wrote:
>
>
> The attached patch does two things:
>
> (1) It gets rid of backing_dev_info::memory_backed and replaces it with a
> pair of boolean values:
>
> (*) dirty_memory_acct
>
> True if the pages associated with this backing device sh
On Wed, 2 Mar 2005, Andrew Morton wrote:
> Kai Makisara <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > v2.6 also contains the same problem BTW.
> > >
> > > Try this:
> > >
> > > --- a/drivers/scsi/st.c.orig 2005-03-02 09:02:13.637158144 -0300
> > > +++ b/drivers/scsi/st.c 2005-03-02 09:0
The EEPROM (or whatever that is) on Asus K8V SE Deluxe motherboards
contains buggy firmware. This buggy firmware has one flipped bit, and
causes the sk98lin driver refuses to work correctly. Please look at
this thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0404.0/1439.html
It contains
On Fri, 2005-03-04 at 04:19 +1100, Nick Piggin wrote:
> You don't want to do that for all architectures, as I said earlier.
> eg. i386 can concurrently set the dirty bit with the MMU (which won't
> honour the lock).
>
> So you then need an atomic lock, atomic pte operations, and atomic
> unlock w
From: Shirley Ma <[EMAIL PROTECTED]>
IPoIB small fixes: Initialize path->ah to NULL, and fix dereference
after free of neigh in error path of neigh_add_path().
Signed-off-by: Shirley Ma <[EMAIL PROTECTED]>
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband
Make IPoIB data_debug_level module parameter static to the single file
where it is used. Also Rename IPoIB module parameter variable from
"debug_level" to "ipoib_debug_level". This avoids possible name
clashes if IPoIB is built into the kernel. We use module_param_named
so that the user-visible
Make hweight() macros return unsigned int for 8,16,32 bits,
instead of requiring callers to do that.
drivers/input/joystick/analog.c:414: warning: int format, different type arg
(arg 3)
drivers/input/joystick/analog.c:414: warning: int format, different type arg
(arg 4)
drivers/input/joystick/a
Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2 Mar 2005, Andrew Morton wrote:
>
> > > Any mmap changes requires the mmapsem.
> >
> > sys_remap_file_pages() will call install_page() under down_read(mmap_sem).
> > It relies upon page_table_lock for pte atomicity.
>
> This is not re
Benjamin Herrenschmidt wrote:
However, if this pte_cmpxchg() thing is used for removing access, then
sparc64 can't use it. In such a case a race in the TLB handler would
result in using an invalid PTE. I could "spin" on some lock bit, but
there is no way I'm adding instructions to the carefully c
100% agree with you, Jeff. That's what I wrote in another mail.
A real -rc should have only a handful of patches. And even more
importantly, the final release MUST be EXACTLY the lastest -rc,
without any new surprize.
Willy
On Wed, Mar 02, 2005 at 11:16:19PM -0500, Jeff Garzik wrote:
> The rea
On Wednesday 02 March 2005 23:28, Jeff V. Merkey wrote:
>Gene Heskett wrote:
>>On Wednesday 02 March 2005 21:36, Jeff V. Merkey wrote:
>>>Another Linux patent.
>>
>>And that pretty much says it. Assigned to the Canopy Group. So
>> SCO will have yet another lawsuit to threaten us with. If the
On sparc32 build, there is a printk format arg-type warning:
fs/proc/proc_misc.c:195: warning: long unsigned int format, unsigned int arg
(arg 23)
I tried to fix it with a change to asm-sparc/vaddrs.h:
-#define VMALLOC_START 0xfe60
+#define VMALLOC_START 0xfe60UL
-#defi
ntfs: Fix printk format warnings on ia64:
fs/ntfs/aops.c:947: warning: long long unsigned int format, long int arg (arg 4)
fs/ntfs/debug.c:169: warning: long long unsigned int format, VCN arg (arg 2)
fs/ntfs/debug.c:169: warning: long long unsigned int format, s64 arg (arg 4)
fs/ntfs/debug.c:174:
Hi,
For an embedded developers perspective, Is there any other advantage of
using initramfs over initrd apart from RAMFS benefits over RAMDISK ?
Please CC me
Thanks
Amol
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
(resend)
Fix gcc warning:
drivers/isdn/i4l/isdn_ppp.c:1581: warning: large integer implicitly truncated
to unsigned type
is unsigned int.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
drivers/isdn/i4l/isdn_ppp.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nau
From: Shirley Ma <[EMAIL PROTECTED]>
Change uses of list_for_each_entry() where the loop variable is freed
inside the loop to list_for_each_entry_safe().
Signed-off-by: Shirley Ma <[EMAIL PROTECTED]>
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband/ulp/i
On Wed, 2 Mar 2005 21:08:07 -0800
Russell Miller <[EMAIL PROTECTED]> wrote:
> How do you know that they won't stop the announcements if this change is made?
Nobody knows such things for sure, let's test it and find out :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Fix up locking for IPoIB path table. Make sure that destruction of
address handles, neighbour info and path structs is locked properly to
avoid races and deadlocks. (Problem originally diagnosed by Shirley Ma)
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infin
From: Shirley Ma <[EMAIL PROTECTED]>
ipoib_put_ah() may call ipoib_free_ah(), which might take the device's
lock. Therefore we need to make sure we don't call ipoib_put_ah()
when holding the lock already.
Signed-off-by: Shirley Ma <[EMAIL PROTECTED]>
Signed-off-by: Roland Dreier <[EMAIL PROTECTE
Add missing break statements in switch in mthca_profile.c (pointed out
by Michael Tsirkin).
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_profile.c
2005-03-02 20:26:03.023831785 -0800
+++ linux-export/drivers/infiniband/hw/mthca/m
Fix memory leak when posting a receive buffer (pointed out by Shirley Ma).
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband/ulp/ipoib/ipoib_ib.c 2005-03-02
20:26:02.919854355 -0800
+++ linux-export/drivers/infiniband/ulp/ipoib/ipoib_ib.c2005-03
On Wed, 2 Mar 2005, David S. Miller wrote:
> Actually, I guess I could do the pte_cmpxchg() stuff, but only if it's
> used to "add" access. If the TLB miss handler races, we just go into
> the handle_mm_fault() path unnecessarily in order to synchronize.
>
> However, if this pte_cmpxchg() thing i
> However, if this pte_cmpxchg() thing is used for removing access, then
> sparc64 can't use it. In such a case a race in the TLB handler would
> result in using an invalid PTE. I could "spin" on some lock bit, but
> there is no way I'm adding instructions to the carefully constructed
> TLB miss
From: Tom Duffy <[EMAIL PROTECTED]>
Fix some sparse warnings by making sure we have appropriate "extern"
declarations visible.
Signed-off-by: Tom Duffy <[EMAIL PROTECTED]>
Signed-off-by: Hal Rosenstock (<[EMAIL PROTECTED]>
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/d
On Thu, Mar 03, 2005 at 12:18:25PM +0900, Kaigai Kohei ([EMAIL PROTECTED])
wrote:
> Hello, Guillaume
>
> I tried to measure the process-creation/destruction performance on
> 2.6.11-rc4-mm1 plus
> some extensiton(Normal/with PAGG/with Fork-Connector).
> But I received a following messages endless
From: Shahar Frank <[EMAIL PROTECTED]>
Fix bug when deregistering a vendor class MAD agent.
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband/core/mad.c 2005-03-02
20:26:03.185796628 -0800
+++ linux-export/drivers/infiniband/core/mad.c 2005-03-02 20
On Wed, 2 Mar 2005, Andrew Morton wrote:
> > There should be no change to these arches
>
> But we must at least confirm that these architectures can make these
> changes in the future. If they make no changes then they haven't
> benefitted from the patch. And the patch must be suitable for all
>
Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2 Mar 2005, Andrew Morton wrote:
>
> > Have the ppc64 and sparc64 people reviewed and acked the change? (Not a
> > facetious question - I just haven't been following the saga sufficiently
> > closely to remember).
>
> There should be no ch
On Thu, 3 Mar 2005 16:00:10 +1100
Paul Mackerras <[EMAIL PROTECTED]> wrote:
> Andrew Morton writes:
>
> > But if the approach which these patches take is not suitable for these
> > architectures then they have no solution to the scalability problem. The
> > machines will perform suboptimally and
Dave Jones wrote:
On Wed, Mar 02, 2005 at 08:38:12PM -0800, Andrew Morton wrote:
> Dave Jones <[EMAIL PROTECTED]> wrote:
> >
> > On Wed, Mar 02, 2005 at 04:00:46PM -0800, Linus Torvalds wrote:
> >
> > > I would not keep regular driver updates from a 2.6. thing.
> >
> > Then the notion of
From: Hal Rosenstock <[EMAIL PROTECTED]>
Remove unneeded MAD agent registration by using a single agent for
both directed-route and LID-routed MADs.
Signed-off-by: Hal Rosenstock <[EMAIL PROTECTED]>
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
--- linux-export.orig/drivers/infiniband/core/a
MTHCA_RESET_VALUE must always be swapped, since the HCA expects to see
it in big-endian order and we write it with writel. This means on
little-endian systems we have to swap it to big-endian order before
writing, and on big-endian systems we need to swap it to make up for
the additional swap that
Here is a batch of fixes from the OpenIB subversion tree for merging.
Thanks,
Roland
-
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
Please read the FAQ at
On Wed, Mar 02, 2005 at 07:46:05AM -0800, Linus Torvalds wrote:
> (In contrast the full ChangeLog was missing because the generation script
> I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3
> or worse, so the log from the last -rc release is fast, but going back all
> t
Andrew Morton wrote:
Christoph Lameter <[EMAIL PROTECTED]> wrote:
On Wed, 2 Mar 2005, Andrew Morton wrote:
Earlier releases back in September 2004 had some pte locking code (and
AFAIK Nick also played around with pte locking) but that
was less efficient than atomic operations.
How much less effici
On Wed, 2 Mar 2005, Andrew Morton wrote:
> Have the ppc64 and sparc64 people reviewed and acked the change? (Not a
> facetious question - I just haven't been following the saga sufficiently
> closely to remember).
There should be no change to these arches
> > Because if a pte is locked it shoul
On Thu, 3 Mar 2005, Paul Mackerras wrote:
> More generally, I would be interested to know what sorts of
> applications or benchmarks show scalability problems on large machines
> due to contention on mm->page_table_lock.
Number crunching apps that use vast amounts of memory through MPI or
large d
On Wed, Mar 02, 2005 at 08:38:12PM -0800, Andrew Morton wrote:
> Dave Jones <[EMAIL PROTECTED]> wrote:
> >
> > On Wed, Mar 02, 2005 at 04:00:46PM -0800, Linus Torvalds wrote:
> >
> > > I would not keep regular driver updates from a 2.6. thing.
> >
> > Then the notion of it being stable i
On Wed, 02 Mar 2005 15:53:36 MST, "Jeff V. Merkey" said:
> __Stable__ would be a good thing. The entire 2.6 development has been a
> disaster from
> a stability viewpoint. I have to maintain a huge tree of patches in
> order to ship appliance
> builds due to the lack of stability for 2.6. I think
J.A. Magallon wrote:
Hi...
I posted this in other mail, but now I can confirm this.
I have a box with a SATA RAID-5, and with 2.6.11-rc3-mm2+libata-dev1
works like a charm as a samba server, I dropped it 12Gb from an
osx client, and people does backups from W2k boxes and everything was fine.
With 2
James Chapman <[EMAIL PROTECTED]> wrote:
>
> Add DS1337 RTC chip driver.
>
drivers/i2c/chips/ds1337.c:60: `I2C_DRIVERID_DS1337' undeclared here (not in a
function)
Also, there are changes in Greg's i2c tree which break your new driver:
drivers/i2c/chips/ds1337.c:60: initializer element is not
On Wednesday 02 March 2005 20:58, David S. Miller wrote:
> That's one of the major things the -rc's don't get. Maybe it gets
> a reference in lwn.net's weekly kernel article, but mostly kernel
> geeks read those and that's not who we want testing -rc's (such
> geeks already are doing so).
>
How d
Andrew Morton writes:
> But if the approach which these patches take is not suitable for these
> architectures then they have no solution to the scalability problem. The
> machines will perform suboptimally and more (perhaps conflicting)
> development will be needed.
We can do a pte_cmpxchg on p
On Wednesday 02 March 2005 19:37, Linus Torvalds wrote:
> That's the whole point here, at least to me. I want to have people test
> things out, but it doesn't matter how many -rc kernels I'd do, it just
> won't happen. It's not a "real release".
>
> In contrast, making it a real release, and makin
On Wed, 2 Mar 2005, Andrew Morton wrote:
> > There have been extensive discussions on all aspects of this patch.
> > This issue was discussed in
> > http://marc.theaimsgroup.com/?t=11069449724&r=1&w=2
>
> This is a difficult, intrusive and controversial patch. Things like the
> above should b
On Wed, 02 Mar 2005 21:32:23 EST, Jeff Garzik said:
> I also note that part of the problem that motivates the even/odd thing
> is a tacit acknowledgement that people only _really_ test the official
> releases.
>
> Which IMHO backs up my opinion that we simply need more frequent releases.
Or mor
Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> > > The cmpxchg will fail if that happens.
> >
> > How about if someone does remap_file_pages() against that virtual address
> > and that syscalls happens to pick the same physical page? We have the same
> > physical page at the same pte slot with d
On Wed, 02 Mar 2005 23:46:22 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> If Linus/DaveM really don't like -pre/-rc naming, I think 2.6.x.y is
> preferable to even/odd.
All of these arguments are circular. If people think that even/odd
will devalue odd releases, guess what 2.6.x.y will do? B
Please do a
bk pull bk://kernel.bkbits.net/jgarzik/libata-upstream-2.4
This will update the following files:
Documentation/Configure.help |5
drivers/scsi/Config.in|1
drivers/scsi/Makefile |1
drivers/scsi/ahci.c | 26 +
drivers/scsi/ata_pii
On Thu, 2005-03-03 at 01:39 -0300, Frédéric L. W. Meunier wrote:
> On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
>
> > On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote:
> >> I just replaced my Matrox G400 with a Jetway Radeon 9600LE
> >> (256Mb). If I run 'modprobe radeonfb', th
On Wednesday 02 March 2005 22:17, Andrew Morton wrote:
>Gene Heskett <[EMAIL PROTECTED]> wrote:
>> Ditto for the 1394 fixes that have been upstream for at
>> least a month, maybe more.
>
>-mm always holds the latest 1394 tree. So you can run -mm, or just
> snarf bk-ieee1394.patch from the broken-
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote:
I just replaced my Matrox G400 with a Jetway Radeon 9600LE
(256Mb). If I run 'modprobe radeonfb', the monitor blanks out
and the power on light keeps flashing.
What may be wrong ? Usin
If Linus/DaveM really don't like -pre/-rc naming, I think 2.6.x.y is
preferable to even/odd.
Just create a 2.6.X repo at each release. For bug fixes to 2.6.X,
commit to this repo, then pull into linux-2.6. For everything else,
pull straight into linux-2.6.
The linux-2.6 repo would be upstrea
Gene Heskett wrote:
On Wednesday 02 March 2005 21:36, Jeff V. Merkey wrote:
Another Linux patent.
And that pretty much says it. Assigned to the Canopy Group. So SCO
will have yet another lawsuit to threaten us with. If they survive
the thrashing I've Been Moved will give them at th
Dave Jones <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 02, 2005 at 04:00:46PM -0800, Linus Torvalds wrote:
>
> > I would not keep regular driver updates from a 2.6. thing.
>
> Then the notion of it being stable is bogus, given how many regressions
> the last few kernels have brought in drivers.
On Wed, Mar 02, 2005 at 01:45:43PM +, Alan Cox wrote:
> On Mer, 2005-03-02 at 08:02, Dave Jones wrote:
> > If there are any of them still being used out there, I'd be even
> > more surprised if they're running 2.6. Then again, there are
> > probably loonies out there running it on 386/486's. 8
Joshua Hudson wrote:
> No obvous reason. Works fine with kernel 2.6.10
>
> Result of lspci:
> 00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
> 00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control
> Registers (rev 02)
> 00:00.3 System peripheral: Intel Corp.
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2 Mar 2005, Andrew Morton wrote:
> >
> > Why not make these bitfields as well?
>
> Side note: bitfields aren't exactly wonderful.
Yup. In this application the fields are initialised once (usually at
compile time) and are never modified. So t
On Wed, Mar 02, 2005 at 05:41:50PM -0500, Jeff Garzik wrote:
> Andrew Morton wrote:
> >Jeff Garzik <[EMAIL PROTECTED]> wrote:
> >
> >>>Thing is, CRYPTO_AES on only selectable on x86.
> >>
> >>You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
> >>the dependencies are a bit weird
David S. Miller wrote:
On Wed, 02 Mar 2005 22:40:57 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
People don't test 2.6-rc releases because they know they are not
"release candidate, with only bug fixes" releases, which is how the rest
of the world interprets the phrase.
That's not %100 true. N
On Wed, Mar 02, 2005 at 02:21:38PM -0800, Linus Torvalds wrote:
> - 2.6.: even at all levels, aim for having had minimally intrusive
>patches leading up to it (timeframe: a week or two)
>
> with the odd numbers going like:
>
> - 2.6.: still a stable kernel, but accept bigger changes leading
On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote:
> I just replaced my Matrox G400 with a Jetway Radeon 9600LE
> (256Mb). If I run 'modprobe radeonfb', the monitor blanks out
> and the power on light keeps flashing.
>
> What may be wrong ? Using 2.6.11.
Do you have a way to captu
On Wednesday 02 March 2005 23:02, Joshua Hudson wrote:
> ACPI: PS/2 Keyboard Controller [KBC] at I/O 0x60, 0x66, irq 1
> ACPI: PS/2 Mouse Controller [PS2M] at irq 12
> i8042.c: Can't read CTR while initializing i8042.
Ok, your BIOS is also reporting incorrect port values for the keyboard
controlle
Dave Jones wrote:
On Wed, Mar 02, 2005 at 07:10:47PM -0800, Randy.Dunlap wrote:
> >For it to truly be a stable kernel, the only patches I'd expect to
> >drivers would be ones fixing blindingly obvious bugs. No cleanups.
> >No new functionality. I'd even question new hardware support if it
> >wa
Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2 Mar 2005, Andrew Morton wrote:
>
> > > This is a related change discussed during V16 with Nick.
> >
> > It's worth retaining a paragraph for the changelog.
>
> There have been extensive discussions on all aspects of this patch.
> This iss
I have an usb-cardreader here that needs some FORCELUN-entries in
scsi_devinfo.c.
lsusb says about the device:
Bus 001 Device 003: ID 0483:1307 SGS Thomson Microelectronics Cytronix 6in1
card reader
Patch see below. Please apply.
--- linux-2.6.11-buju/drivers/scsi/scsi_devinfo.c 2005-
I committed to a fairly complex project to run on Linux while
assuming that the Linux stack implementation would provide
equivalent functionality to that of the BSD-style stacks I am
familiar with. At this point, quite far down the design path,
I looked at what I thought would be trivial details
On Wed, 02 Mar 2005 21:32:23 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> I also note that part of the problem that motivates the even/odd thing
> is a tacit acknowledgement that people only _really_ test the official
> releases.
>
> Which IMHO backs up my opinion that we simply need more fre
In article <[EMAIL PROTECTED]> (at Wed, 2 Mar 2005 19:37:44 -0800 (PST)), Linus
Torvalds <[EMAIL PROTECTED]> says:
> In contrast, making it a real release, and making it clear that it's a
> release in its own right, might actually get people to use it.
>
> Might. Maybe.
I believe people soon
Joerg Sommrey wrote:
Jeff Garzik wrote:
BK users:
bk pull bk://gkernel.bkbits.net/libata-dev-2.6
Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
Still not usable here. The same errors as before when backing up:
Please try 2.6.11 without
PCI: Using ACPI for IRQ routing
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Lid Switch [LID]
ACPI: Power Button (CM) [PBTN]
ACPI: Sleep Button (CM) [SBTN]
ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
ACPI: Video Device [VID2] (multi-head: yes
This patch changes bcu.c to calculate clock at any time.
Because clock can be changed.
Moreover, EXPORT_SYMBOL_GPLs are added to it.
Yoichi
Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]>
diff -urN -X dontdiff a-orig/arch/mips/vr41xx/common/bcu.c
a/arch/mips/vr41xx/common/bcu.c
--- a-orig/arch/
On Wed, 02 Mar 2005 22:40:57 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> People don't test 2.6-rc releases because they know they are not
> "release candidate, with only bug fixes" releases, which is how the rest
> of the world interprets the phrase.
That's not %100 true. No matter what -rc
On Wed, 2 Mar 2005 14:21:38 -0800 (PST), Linus Torvalds
<[EMAIL PROTECTED]> wrote:
>
> Comments?
>
Just rename:
2..-rcX -> 2..y-preX
2.. -> 2..y-rcX
2.. -> 2..y
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Wed, Mar 02, 2005 at 07:10:47PM -0800, Randy.Dunlap wrote:
> >For it to truly be a stable kernel, the only patches I'd expect to
> >drivers would be ones fixing blindingly obvious bugs. No cleanups.
> >No new functionality. I'd even question new hardware support if it
> >wasn't just a PCI I
On Wed, Mar 02, 2005 at 02:21:38PM -0800, Linus Torvalds wrote:
>
> This is an idea that has been brewing for some time: Andrew has mentioned
> it a couple of times, I've talked to some people about it, and today Davem
> sent a suggestion along similar lines to me for 2.6.12.
>
> Namely tha
On Wed, Mar 02, 2005 at 02:21:38PM -0800, Linus Torvalds wrote:
> The problem with major development trees like 2.4.x vs 2.5.x was that the
> release cycles were too long, and that people hated the back- and
> forward-porting. That said, it did serve a purpose - people kind of knew
> where they
Hi.
My first response is: this is a recipe for great confusion among users.
I'd far rather see things only make it into your tree when they've been
thoroughly tested (in -mm and prior to that). Following that strategy,
your tree could always be relied upon to be stable and -rcs would only
needed
Hi,
On Wed, Mar 02, 2005 at 12:31:23PM -0800, Andrew Morton wrote:
> Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> >
> > Do you have any objections to merging FUSE in mainline kernel?
>
> I was planning on sending FUSE into Linus in a week or two. That and
> cpusets are the notable features whic
Jeff Garzik wrote:
On Thu, Mar 03, 2005 at 12:39:41AM +, J.A. Magallon wrote:
Hi...
I posted this in other mail, but now I can confirm this.
I have a box with a SATA RAID-5, and with 2.6.11-rc3-mm2+libata-dev1
works like a charm as a samba server, I dropped it 12Gb from an
osx client, and peopl
Linus Torvalds wrote:
On Wed, 2 Mar 2005, Jeff Garzik wrote:
If we want a calming period, we need to do development like 2.4.x is
done today. It's sane, understandable and it works.
No. It's insane, and the only reason it works is that 2.4.x is a totally
different animal. Namely it doesn't have
On Wed, 2 Mar 2005, Jeff Garzik wrote:
>
> If we want a calming period, we need to do development like 2.4.x is
> done today. It's sane, understandable and it works.
No. It's insane, and the only reason it works is that 2.4.x is a totally
different animal. Namely it doesn't have the kind of a
On Wednesday 02 March 2005 17:33, David Johnson wrote:
> On Wednesday 02 Mar 2005 22:03, Dmitry Torokhov wrote:
> > On Wed, 2 Mar 2005 21:35:16 +, David Johnson <[EMAIL PROTECTED]> wrote:
> > > Hi all,
> > >
> > > I've just booted 2.6.11 and the keyboard on my Dell Inspiron 5150 laptop
> > > do
1 - 100 of 458 matches
Mail list logo
