On 290, 10 17, 2007 at 06:16:58 -0400, Chris Bergeron wrote:
> Andrey Panin wrote:
>>
>> Is it possible to connect two ports and run getty on one port and minicom
>> on
>> another ? We should check that UARTs are really working.
>>
>>
> I used the on-board serial port as a known working
From: Michael Hennerich <[EMAIL PROTECTED]>
Cc: Andrey Panin <[EMAIL PROTECTED]>
Signed-off-by: Michael Hennerich <[EMAIL PROTECTED]>
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
drivers/input/keyboard/bf54x-keys.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Mark Lord wrote:
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the
usb 5-1: new high speed USB device using ehci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
hub 5-1:1.0: USB hub found
hub 5-1:1.0: 4 ports detected
sysfs: duplicate filename 'bInterfaceNumber' can not be created
WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
On Wed, Oct 17, 2007 at 02:16:19PM +0900, Ken'ichi Ohmichi wrote:
>
> Hi Simon,
>
> Simon Horman wrote:
> > On Wed, Aug 22, 2007 at 09:13:39PM +0900, Ken'ichi Ohmichi wrote:
> >> [2/3] [kexec-tools] Pass vmcoreinfo's address and size
> >> The patch is for kexec-tools-testing-20070330.
> >>
Hi,
Kernel oops is triggered within few seconds after boot up in ia64 machine
[ 113.004837] Unable to handle kernel NULL pointer dereference (address
0022)
[ 113.013077] tail[3466]: Oops 8813272891392 [1]
[ 113.017643] Modules linked in:
[ 113.020854]
[ 113.020855] Pid: 3466,
Try this patch and report back again:
http://lkml.org/lkml/2007/10/17/269
-
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
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the meantime, does the patch
From: rajashok <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2007 22:10:43 -0700 (PDT)
> we are trying to to integrate our ipsec onto linux 2.6 kernel
Why not use the already existing 2.6.x kernel IPSEC stack?
It works quite well.
And for this reason, it is unlikely you will get much help
on these
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the meantime, does the patch I sent out help
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
> I guess now that I've written this out, it seems pretty clear
> that capget64() and capget64() are the way to go. Any objections?
How is capget64() different from capget() that supports 2 different
header->versions (I thought that was the whole
On Thursday 18 October 2007 13:59, Eric W. Biederman wrote:
> If filesystems care at all they want absolute control over the buffer
> cache. Controlling which buffers are dirty and when. Because we
> keep the buffer cache in the page cache for the block device we have
> not quite been giving
On Thu, Oct 18, 2007 at 05:57:05AM +0100, Al Viro wrote:
> On Tue, Oct 16, 2007 at 09:17:40PM -0700, Casey Schaufler wrote:
> Think what happens if CPU1 adds to list and CPU2 sees write to smk_known
> *before* it sees write to ->smk_next. We see a single-element list and
> we'll be lucky if that
Mark Lord wrote:
Mark Lord wrote:
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to
test
patches against latest -git in time for the current merge
Greetings,
When shutting down this kernel, my box is hanging when the init scripts
tries to set the hardware clock, so I fired up my serial console box,
and set nmi_watchdog=2, but nothing happened. When I poked SysRq-T
however, I received the below. I also notice that I can't login via
serial
On Tue, Oct 16, 2007 at 09:17:40PM -0700, Casey Schaufler wrote:
At random:
> +static int smack_netlabel(struct sock *sk)
> +{
> + static int initialized;
> + struct socket_smack *ssp = sk->sk_security;
> + struct netlbl_lsm_secattr secattr;
> + int rc = 0;
> +
> + if
Mark Lord wrote:
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the
From: Márton Németh <[EMAIL PROTECTED]>
As DRM_DEBUG macro already prints out the __FUNCTION__ string (see
drivers/char/drm/drmP.h), it is not worth doing this again. At some
other places the ending "\n" was added.
Signed-off-by: Márton Németh <[EMAIL PROTECTED]>
---
diff -uprN
On Thu, 18 Oct 2007, Jeff Garzik wrote:
>
> Is this a sata_mv box? If so, could you try this patch?
That could explain it: if the SG allocation is simply too small, the
scatter-gather code will run off the end of the SG list, and encounter
random uninitialized entries, and if any of those
thanks, applied 1-5
-
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 http://www.tux.org/lkml/
On Thu, 18 Oct 2007, Mark Lord wrote:
>
> Okay, mine is dying with EIP at blk_rq_map_sg+0xcb/0x160.
Ok, I think your picture cut off the last hex digits on the right, but
what I can make out of the disassembly, I have to admit that it looks
very much like it might be exactly the same thing
Jeff Garzik wrote:
Mark Lord wrote:
Okay, mine is dying with EIP at blk_rq_map_sg+0xcb/0x160.
Screen photo is at http://rtr.ca/recent/2.6.23-git12-crash.jpg,
but the top was cut off (isn't there a new config option or patch
to do double-columns or scrollback or something ???.
Is this a
On Wed, 17 Oct 2007 21:59:02 -0600 [EMAIL PROTECTED] (Eric W. Biederman) wrote:
> If filesystems care at all they want absolute control over the buffer
> cache. Controlling which buffers are dirty and when. Because we
> keep the buffer cache in the page cache for the block device we have
> not
On Wed, Oct 17, 2007 at 01:36:51PM +0200, Bernhard Walle wrote:
[..]
> > > +static int __init reserve_bootmem_core(bootmem_data_t *bdata, unsigned
> > > long addr,
> > > + unsigned long size, int flags)
> > > {
> > > unsigned long sidx, eidx;
> > > unsigned
Mark Lord wrote:
Okay, mine is dying with EIP at blk_rq_map_sg+0xcb/0x160.
Screen photo is at http://rtr.ca/recent/2.6.23-git12-crash.jpg,
but the top was cut off (isn't there a new config option or patch
to do double-columns or scrollback or something ???.
Is this a sata_mv box? If so,
Greetings,
Freshly pulled tree oopes per $subject.
[ 114.714335] BUG: unable to handle kernel NULL pointer dereference at virtual
address 0031
[ 114.732810] printing eip: c03332ff *pde =
[ 114.747614] Oops: [#1] PREEMPT SMP
[ 114.761320] Modules linked in: microcode
Maxim Levitsky wrote:
Probably everything is fine.
I added a new mixer control called "Master Volume"
it is a VolumeKnob.
It is a hardware control, that was unused in the driver before.
It affects the volume of all DACs
check if it is enabled, and set to maximum value.
This control affects
On Thu, 18 Oct 2007, Mark Lord wrote:
>
> Oh.. so this bug is supposed to only bite with DEBUG_PAGEALLOC=y ??
Yeah, this particular one really should only bite you with
DEBUG_PAGEALLOC.
The SG code potentially _derefences_ a field past the end of the SG array,
but it should be a read, and
On Mon, 15 Oct 2007 13:32:24 -0500 Jason Wessel <[EMAIL PROTECTED]> wrote:
> This is a request to merge KGDB into the mainline kernel.
This won't work very well. There's a lot of review work to be done here,
and a lot of it by busy architecture maintainers. Expecting people to do
all this
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the meantime, does the patch
Mark Lord wrote:
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the meantime, does the patch
On Thursday 18 October 2007 05:38:06 Jeff Garzik wrote:
> Maxim Levitsky wrote:
> > What sound codec do you have?
> > cat /proc/asound/Intel/codec*
>
> Attached.
>
> I'm on x86-64/Fedora 7 FWIW.
>
>
> > You probably have different issue, since your card is probed correctly
>
> Agreed (though
On Thu, 11 Oct 2007 13:18:49 +0200 Jan Kara <[EMAIL PROTECTED]> wrote:
> With 64KB blocksize, a directory entry can have size 64KB which does not fit
> into 16 bits we have for entry lenght. So we store 0x instead and convert
> value when read from / written to disk.
btw, this changes ext2's
On Thu, 11 Oct 2007 13:18:49 +0200 Jan Kara <[EMAIL PROTECTED]> wrote:
> +static inline __le16 ext2_rec_len_to_disk(unsigned len)
> +{
> + if (len == (1 << 16))
> + return cpu_to_le16(EXT2_MAX_REC_LEN);
> + else if (len > (1 << 16))
> + BUG();
> + return
Linus Torvalds wrote:
On Wed, 17 Oct 2007, Mark Lord wrote:
It would be good to have something soon-ish.
This "dead at boot time" issue is impacting the general ability to test
patches against latest -git in time for the current merge window.
In the meantime, does the patch I sent out help
On Wed, 17 Oct 2007, Mark Lord wrote:
>
> It would be good to have something soon-ish.
> This "dead at boot time" issue is impacting the general ability to test
> patches against latest -git in time for the current merge window.
In the meantime, does the patch I sent out help people? I'd like
If filesystems care at all they want absolute control over the buffer
cache. Controlling which buffers are dirty and when. Because we
keep the buffer cache in the page cache for the block device we have
not quite been giving filesystems that control leading to really weird
bugs.
In addition
Kgdb has been submitted for inclusion in the mainline kernel at this
point, along with an additional change to the netpoll rx path.
If it is the case that this needs to be implemented in another manner,
that is ok but please do let me know what the plans are for the API so
that the kgdboe code
On Thu, 18 Oct 2007 12:25:37 +0900 Yasunori Goto <[EMAIL PROTECTED]> wrote:
>
> This patch fixes panic due to access NULL pointer
> of kmem_cache_node at discard_slab() after memory online.
>
> When memory online is called, kmem_cache_nodes are created for
> all SLUBs for new node whose memory
Linus Torvalds wrote:
On Wed, 17 Oct 2007, David Miller wrote:
I believe that we have enough of a limited set of accessors to
sg->page that we can more aggressively encode things in the lower
bits.
I'm thinking of encoding the low two bits of sg->page as
follows:
...
Yes, that sounds sane.
On Thu, 18 Oct 2007 12:23:34 +0900 Yasunori Goto <[EMAIL PROTECTED]> wrote:
> writeback_set_ratelimit();
> +
> + if (onlined_pages)
> + memory_notify(MEM_ONLINE, );
perhaps that open-coded writeback_set_ratelimit() should become a
notifier callback.
-
To unsubscribe from
Maxim Levitsky wrote:
What sound codec do you have?
cat /proc/asound/Intel/codec*
Attached.
I'm on x86-64/Fedora 7 FWIW.
You probably have different issue, since your card is probed correctly
Agreed (though I was surprised that a correct probe did not yield a
single printk).
On Thursday 18 October 2007 04:35:56 Jeff Garzik wrote:
> Thomas Meyer wrote:
> > $ dmesg
> >
> > [schnipp]
> >
> > ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
> > PCI: Enabling bus mastering for device :00:1b.0
> > PCI: Setting latency timer of device :00:1b.0
(repost to conform with akpm's subject line conventions)
Make use of the previously split out pcie_init_enable_events() function
to reinitialize the hotplug hardware on resume from suspend,
but only when pciehp_force==1. Otherwise behaviour is unmodified.
Signed-off-by: Mark Lord <[EMAIL
(repost to conform with akpm's subject line conventions)
One of three patches to fix PCIe Hotplug so that it works with ExpressCard slots
on Dell notebooks (and others?) in conjunction with modparam of pciehp_force=1
Split out the hotplug hardware initialization code from pcie_init()
into
(repost to conform with akpm's subject line conventions)
One of three patches to fix PCIe Hotplug so that it works with ExpressCard slots
on Dell notebooks (and others?) in conjunction with modparam of pciehp_force=1.
Fix pciehp_probe() to deal with ExpressCard cards
that were inserted prior to
Chris Mason <[EMAIL PROTECTED]> writes:
> On Wed, 2007-10-17 at 17:28 -0600, Eric W. Biederman wrote:
>> Chris Mason <[EMAIL PROTECTED]> writes:
>>
>> > So, the problem is using the Dirty bit to indicate pinned. You're
>> > completely right that our current setup of buffer heads and pages and
On Wed, 17 Oct 2007 21:59:20 -0500 "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
> Quoting Andrew Morton ([EMAIL PROTECTED]):
> > On Tue, 16 Oct 2007 16:41:59 -0500
> > "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
> >
> > > To properly test this the libcap code will need to be updated first,
> >
This patch fixes panic due to access NULL pointer
of kmem_cache_node at discard_slab() after memory online.
When memory online is called, kmem_cache_nodes are created for
all SLUBs for new node whose memory are available.
slab_mem_going_online_callback() is called to make kmem_cache_node()
in
Current memory notifier has some defects yet. (Fortunately, nothing uses it.)
This patch is to fix and rearrange for them.
- Add information of start_pfn, nr_pages, and node id if node status is
changes from/to memoryless node for callback functions.
Callbacks can't do anything without
Add description about event notification callback routine to the document.
Signed-off-by: Yasunori Goto <[EMAIL PROTECTED]>
---
Documentation/memory-hotplug.txt | 58 ---
1 file changed, 55 insertions(+), 3 deletions(-)
Index:
Hello.
This patch set is to rearrange event notifier for memory hotplug,
because the old notifier has some defects. For example, there is no
information like new memory's pfn and # of pages for callback functions.
Fortunately, nothing uses this notifier so far, there is no impact by
this change.
Linus Torvalds wrote:
On Wed, 26 Sep 2007, Mark Lord wrote:
The existing code in linux/drivers/acpi/sleep/proc.c has a nasty bug
that prevents BCD mode from working: the code converts binary to BCD
three times in a row, each time taking the previous result.
This thoroughly mangles the alarm
On Wed, 17 Oct 2007 19:56:36 -0700 (PDT)
[EMAIL PROTECTED] (Paul Menage) wrote:
> + seq_printf(m, "%s\t%d\t%d\n",
> +ss->name, ss->root->subsys_bits,
> +ss->root->number_of_cgroups);
> }
Because subsys_bits is unsigned long, then
--- "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
> Quoting Andrew Morton ([EMAIL PROTECTED]):
> > On Tue, 16 Oct 2007 16:41:59 -0500
> > "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
> >
> > > To properly test this the libcap code will need to be updated first,
> > > which I'm looking at now...
Mark Lord wrote:
Fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks
(and others?) in conjunction with the modparam of pciehp_force=1.
To make things simpler for distro people, I'm contemplating another patch
in this series, to allow something like: pciehp_force=2
On Wed, 17 Oct 2007 18:34:16 -0700
"Thomas Fricaccia" <[EMAIL PROTECTED]> wrote:
>
> But then I noticed that, while the LSM would remain in existence, it
> was being closed to out-of-tree security frameworks. Yikes! Since
> then, I've been following the rush to put SMACK, TOMOYO and AppArmor
>
Kristen,
If you're happy with this set, please add your Acked-by (or whatever).
Thanks,
Mark
-
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
01_pciehp_handle_preinserted_card.patch:
Fix pciehp_probe() to deal with ExpressCard cards
that were inserted prior to the driver being loaded.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
--- git12/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 22:30:19.0
-0400
+++
02_pciehp_split_pcie_init.patch:
Split out the hotplug hardware initialization code from pcie_init()
into pcie_init_enable_events(), without changing any functionality.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
--- git12/drivers/pci/hotplug/pciehp_hpc.c 2007-10-17 19:06:38.0
03_pciehp_resume_reinit_hardware.patch:
Make use of the previously split out pcie_init_enable_events() function
to reinitialize the hotplug hardware on resume from suspend,
but only when pciehp_force==1. Otherwise behaviour is unmodified.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
---
02_pciehp_split_pcie_init.patch:
Split out the hotplug hardware initialization code from pcie_init()
into pcie_init_enable_events(), without changing any functionality.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
--- git12/drivers/pci/hotplug/pciehp_hpc.c 2007-10-17 19:06:38.0
Quoting Andrew Morton ([EMAIL PROTECTED]):
> On Tue, 16 Oct 2007 16:41:59 -0500
> "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
>
> > To properly test this the libcap code will need to be updated first,
> > which I'm looking at now...
>
> This seems fairly significant. I asusme that this patch
01_pciehp_handle_preinserted_card.patch:
Fix pciehp_probe() to deal with ExpressCard cards
that were inserted prior to the driver being loaded.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
--- git12/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 22:30:19.0
-0400
+++
>
> In general, I tend to think that for this function to make any sense
> (that is, to synchronize anything at all), it needs a barrier or you are
> just making a decision based on a totally random value of desc->status
> since it can have been re-ordered, speculatively loaded, pre-fetched,
>
Fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks
(and others?) in conjunction with the modparam of pciehp_force=1.
The PCIe Hotplug driver has two issues when used on Dell notebooks
which lack ACPI BIOS support for PCIe hotplug:
1. The driver does not recognise cards
This patch simplifies /proc/cgroups by removing pointers and some
debugging information, and simply presenting a list of subsystems,
which hierarchy they are part of (if any) and the number of cgroups
created for that subsystem. Hierarchy id is determined by the bitmask
of subsystem ids attached
On Wed, Oct 17, 2007 at 06:19:53PM -0500, Eric Van Hensbergen wrote:
> On 10/17/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> > On Wed, Oct 17, 2007 at 04:34:02PM -0500, Eric Van Hensbergen wrote:
> > > Linus, please pull from the 'for-linus' branch of:
> > >
On Wed, 2007-10-17 at 19:12 -0700, Linus Torvalds wrote:
>
> So, what exactly does it protect against? At a minimum, this needs a
> comment in the changelog, and probably preferably in the source code too.
I replied to Andrew, but I agree, it's worth a comment, I'll add one.
> The thing is,
From: Matthias Kaehlcke <[EMAIL PROTECTED]>
Date: Tue, 16 Oct 2007 19:18:52 +0200
> Videopix Frame Grabber: Convert the semaphore device_lock_sem to the
> mutex API
>
> Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
Applied, thanks.
-
To unsubscribe from this list: send the line
Thomas Meyer wrote:
$ dmesg
[schnipp]
ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
PCI: Enabling bus mastering for device :00:1b.0
PCI: Setting latency timer of device :00:1b.0 to 64
hda_codec: STAC922x, Apple subsys_id=106b0200
ACPI: PCI interrupt for device
From: Charles Hardin <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2007 14:36:10 -0700
> Kernel needs to respond to an SADB_GET with the same message type to conform
> to the RFC 2367 Section 3.1.5
I can't apply this:
1) We need you to provide an appropriate Signed-off-by: line
in the changelog of
Kristen Carlson Accardi wrote:
On Tue, 16 Oct 2007 21:55:30 -0400
Mark Lord <[EMAIL PROTECTED]> wrote:
Make use of the previously split out pcie_init_enable_events() function
to reinitialize the hotplug hardware on resume from suspend,
but only when pciehp_force==1. Otherwise behaviour is
Kristen Carlson Accardi wrote:
On Tue, 16 Oct 2007 21:54:42 -0400
Mark Lord <[EMAIL PROTECTED]> wrote:
Fix pciehp_probe() to deal with pre-inserted ExpressCard cards,
but only when pciehp_force==1. Otherwise behaviour is unmodified.
I think it would be ok to try allowing the slot to be
On Wed, 17 Oct 2007, Casey Schaufler wrote:
>
> The in-tree vs out-of-tree discussion is independent of LSM.
Indeed. I think there is certainly likely to be some small overlap, but I
*think* they are largely independent issues - "do we want choice in
securitu models" (a very emphatic YES as
On Wed, 17 Oct 2007, Thomas Fricaccia wrote:
>
> But then I noticed that, while the LSM would remain in existence, it was
> being closed to out-of-tree security frameworks. Yikes! Since then,
> I've been following the rush to put SMACK, TOMOYO and AppArmor
> "in-tree".
Yeah, it did come
On Thu, 18 Oct 2007, Benjamin Herrenschmidt wrote:
>
> + smp_mb();
> while (desc->status & IRQ_INPROGRESS)
> cpu_relax();
So, what exactly does it protect against? At a minimum, this needs a
comment in the changelog, and probably preferably in the source code too.
--- Thomas Fricaccia <[EMAIL PROTECTED]> wrote:
> ...
>
> But then I noticed that, while the LSM would remain in existence, it was
> being closed to out-of-tree security frameworks. Yikes! Since then, I've
> been following the rush to put SMACK, TOMOYO and AppArmor "in-tree".
>
> Since I
> > Index: linux-work/kernel/irq/manage.c
> > ===
> > --- linux-work.orig/kernel/irq/manage.c 2007-10-18 11:22:16.0
> > +1000
> > +++ linux-work/kernel/irq/manage.c 2007-10-18 11:22:20.0 +1000
> > @@ -33,6 +33,7
>From 0824b077b75c19253b45c5a455775c331acd54ee Mon Sep 17 00:00:00 2001
From: Maxim Levitsky <[EMAIL PROTECTED]>
Date: Thu, 18 Oct 2007 03:35:37 +0200
Subject: [PATCH] [HDA] [STAC] Since there is now a master volume control,
don't call the headphone output "Master", it isn't strictly correct
On 10/17/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Oct 2007, Matthew Dharm wrote:
>
> > On Tue, Oct 16, 2007 at 02:04:43PM -0400, Alan Stern wrote:
> > > On Tue, 16 Oct 2007, Matthew Dharm wrote:
> > >
> > > > I haven't looked at this code at all, but neither approach feels right
> >
Hi,
I understand why this happens.
Your sound card has a single "headphone" output, and since it is single, it is
called "Master"
the stac you have also has a real master volume control, that controls all the
DACs, not just the headphones.
I added support for it, thus two controls collided.
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2007 18:36:34 -0700 (PDT)
> Although I also wonder whether we want one global per-arch
> ARCH_HAS_SG_CHAIN
It's there because the DMA mapping support code for a platform has to
be converted to handle these chains and audited to make
On Thu, Oct 18, 2007 at 10:07:54AM +1000, Paul Mackerras wrote:
> The correct fix is to make advansys depend on CONFIG_VIRT_TO_BUS, or
> alternatively fix advansys.c properly by making it use the interfaces
> described in Documentation/DMA-mapping.txt (or the equivalent scsi
> helpers).
If you
On Thu, 18 Oct 2007 11:25:42 +1000
Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> synchronize_irq needs at the very least a compiler barrier and a
> read barrier on SMP,
Why?
> but there are enough cases around where a
> write barrier is also needed and it's not a hot path so I prefer
>
Like many of us who earn a good living with Linux (for over a decade now) and
follow the kernel developer discussions with waxing and waning interest
depending on topic, I noticed James Morris' proposal to eliminate the LSM in
favor of ordaining SELinux as THE security framework forever and
On Wed, 17 Oct 2007, David Miller wrote:
>
> I believe that we have enough of a limited set of accessors to
> sg->page that we can more aggressively encode things in the lower
> bits.
>
> I'm thinking of encoding the low two bits of sg->page as
> follows:
>
> 1) bits == 0
>
>then the SG
Robert Hancock wrote:
This doesn't seem a very reliable way to identify an IDE device, as all
that 0 means is that the device does not claim conformance to any
standard. I would think it would be legitimate for an IDE device to put
a value like 5 in there as well, if it complies with SPC-4..
synchronize_irq needs at the very least a compiler barrier and a
read barrier on SMP, but there are enough cases around where a
write barrier is also needed and it's not a hot path so I prefer
using a full smp_mb() here.
It will degrade to a compiler barrier on !SMP.
Signed-off-by: Benjamin
(cc-ing linux-ide)
Mathieu Fluhr wrote:
Hello all,
First of all, let me introduce myself a little bit. I am the responsable
for the development of the Nero Linux burning application. So I have
access to all the source code of the application.
Now let's go with the story: It seems that there
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2007 18:07:19 -0700 (PDT)
> sg_next() - as it stands now - never actually looks at the SG that its
> argument points to: it explicitly *only* looks at the next one.
>
> That's the bug. If sg_next() looked at the actual *current* sg
On a related hardware note:
FWIW, most ATA controllers have scatter/gather tables that terminate
themselves by a bit in the final s/g entry. The 90% case needs to know
the last scatterlist entry, at the end of the s/g walk.
So however this all gets worked out, please make sure not to unduly
Well, the new driver is not a fix.
Anyway -- still plugging away at debugging libata. It seems some
outside changes are causing a bunch of my test boxes to crap themselves.
These need to go up in the meantime, however.
Maybe its the sg-chaining stuff, we'll see. I'm watching that thread
On Thursday 18 October 2007 04:45, Eric W. Biederman wrote:
> At this point my concern is what makes a clean code change in the
> kernel. Because user space can currently play with buffer_heads
> by way of the block device and cause lots of havoc (see the recent
Well if userspace is writing to
On Thu, 18 Oct 2007, FUJITA Tomonori wrote:
>
> Looks that (sglist) - 1 isn't initialized and we use sg_next for it?
sg_next() - as it stands now - never actually looks at the SG that its
argument points to: it explicitly *only* looks at the next one.
That's the bug. If sg_next() looked at
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-linus
to receive the following updates:
drivers/net/3c59x.c|2 +-
drivers/net/forcedeth.c| 27 ++---
On Tue, 16 Oct 2007 16:41:59 -0500
"Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
> To properly test this the libcap code will need to be updated first,
> which I'm looking at now...
This seems fairly significant. I asusme that this patch won't break
presently-deployed libcap?
-
To unsubscribe
The async_tx interface includes a completion callback. This adds support
for using that callback, including using interrupts on completion.
This second try does better at defining the callback prototype.
Cc: David Miller <[EMAIL PROTECTED]>
Signed-off-by: Shannon Nelson <[EMAIL PROTECTED]>
---
Sonic Zhang wrote:
Changes:
1. Remove irq_ack() and port_disable() methods
2. Acocomodate for the libata-link patches
3. Change Kconfig ATAPI mode option into a module param.
4. Add supported WMDMA mode.
Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list:
Reorder the pci release actions
Letting go of the resources in the right order helps get rid of
occasional kernel complaints.
Fix the pci_driver object name [Randy Dunlap]
Rename the struct pci_driver data so that false section mismatch
warnings won't be produced.
Cc: Randy
1 - 100 of 1134 matches
Mail list logo
