Linus Torvalds wrote:
On Sat, 22 Dec 2007, Arjan van de Ven wrote:
On Sat, 22 Dec 2007 09:20:06 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
Yuck. And, Linus is just being silly. Wait a year then turn on
MMCONFIG :) It took PCI MSI a while to mature, but is finally
getting
Arjan van de Ven wrote:
On Sat, 22 Dec 2007 20:30:58 +0100
Martin Mares [EMAIL PROTECTED] wrote:
Hello!
Just make it so. The name is fine, the concept is unavoidable. The
people who complain are whiners that haven't ever had to deal with
the fact that there are broken machines around.
I
Arjan van de Ven wrote:
On Sat, 22 Dec 2007 09:20:06 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space
(using MCFG acpi table etc) to be opt-in, since there's many issues
with it and most drivers don't even
Linus Torvalds wrote:
The problem is that it isn't enough that it works on common machines with
good hardware. The problem is that we end up chasing insane bugs, wasting
peoples valuable time and effort, on those *few* - out of *millions* - of
machines that then surprisingly don't work.
And
Linus Torvalds wrote:
On Sat, 22 Dec 2007, Jeff Garzik wrote:
Regardless of whether a driver is loaded or not, you may NEED to see extended
capabilities. The system may NEED to see those capabilities just to parse
them for sane operation.
And that's just not true.
I don't know why you even
Jeff Garzik wrote:
Maybe that day will never come, but it is nonetheless quite possible
without today's PCI Express spec for this to happen.
er, s/without/within/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Linus Torvalds wrote:
On Sat, 22 Dec 2007, Jeff Garzik wrote:
My core assertion: the present situation -- turning off MMCONFIG aggressively
-- is greatly preferable to adding pci_enable_mmconfig_accesses(pdev).
Well, you do realize that right now we have to have _users_ just doing
pci
Linus Torvalds wrote:
I want to limit that downside. Right now, the easiest way to limit it
seems to be to say that those (very very few) drivers that actually care
could enable it. That way, we automatically limit it to only those
machines that have hardware that cares.
Then let's do it
Linus Torvalds wrote:
On Sat, 22 Dec 2007, Jeff Garzik wrote:
But regardless of problems, enabling should be done globally, not per
device...
I'm ok with trying the globally idea, but it has to be globally but
only if absolutely required.
And quite frankly, how do you tell whether it's
Linus Torvalds wrote:
On Sun, 23 Dec 2007, Jeff Garzik wrote:
And yes, if you want the capability following to notice automatically when
capabilities really do go into the 0x100+ range, that's fine. I suspect
Yes, we /must/ do this checking, if we don't already.
Hell no. If the user asked
Loic Prylli wrote:
Supporting extended-conf-space is independant of the issue of using
mmconf for legacy conf-space.
True.
There is no real reason to use the same
method to access both. I have seen several arguments used that were
implying that, and they all seem really bogus to me. Not
Al Viro wrote:
On Sun, Dec 23, 2007 at 12:33:14AM -0500, Jeff Garzik wrote:
A couple [minorly] notable wireless bug fixes, and plenty of viro fixes
for obscure issues :)
Heh... FWIW, forcedeth patch (sent your way about two weeks ago) also
belongs in the same set. If you need a resend
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
applied 1-2 to #upstream
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
A couple serious fixes (wireless, e100, sky2) and a bevy of minor ones.
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:
MAINTAINERS|6 ++
In 2.6.24, we turned on ACPI support in libata. This is needed in order
to support suspend/resume and BIOS passworded drives, but it inevitably
brought with it a host of new regressions -- which is what happens
anytime you blindly accept ATA commands the BIOS has decided to toss
your way. :)
Mark Lord wrote:
Improve the existing boot/load time warnings from sata_mv
for Highpoint RocketRAID 23xx cards, based on new knowledge
about where the BIOS likes to overwrite sectors with metadata.
Harmless to us, but very useful for end users.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
Jochen Friedrich wrote:
This patch adds support to use the fixed-link property
of an ethernet node to fs_enet for the
CONFIG_PPC_CPM_NEW_BINDING case.
Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
---
drivers/net/fs_enet/fs_enet-main.c |9 -
1 files changed, 8 insertions(+),
Andrew Gallatin wrote:
Remove the bogus netif_running() check from myri10ge_poll().
This eliminates any chance that myri10ge_poll() can trigger
an oops by calling netif_rx_complete() and returning
with work_done == budget.
Signed-off-by: Andrew Gallatin <[EMAIL PROTECTED]>
holding onto this
Andrew Gallatin wrote:
Remove the bogus netif_running() check from myri10ge_poll().
This eliminates any chance that myri10ge_poll() can trigger
an oops by calling netif_rx_complete() and returning
with work_done == budget.
Signed-off-by: Andrew Gallatin [EMAIL PROTECTED]
holding onto this
Jochen Friedrich wrote:
This patch adds support to use the fixed-link property
of an ethernet node to fs_enet for the
CONFIG_PPC_CPM_NEW_BINDING case.
Signed-off-by: Jochen Friedrich [EMAIL PROTECTED]
---
drivers/net/fs_enet/fs_enet-main.c |9 -
1 files changed, 8 insertions(+), 1
Mark Lord wrote:
Improve the existing boot/load time warnings from sata_mv
for Highpoint RocketRAID 23xx cards, based on new knowledge
about where the BIOS likes to overwrite sectors with metadata.
Harmless to us, but very useful for end users.
Signed-off-by: Mark Lord [EMAIL PROTECTED]
---
In 2.6.24, we turned on ACPI support in libata. This is needed in order
to support suspend/resume and BIOS passworded drives, but it inevitably
brought with it a host of new regressions -- which is what happens
anytime you blindly accept ATA commands the BIOS has decided to toss
your way. :)
A couple serious fixes (wireless, e100, sky2) and a bevy of minor ones.
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:
MAINTAINERS|6 ++
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
applied 1-2 to #upstream
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Adrian Bunk wrote:
On Fri, Dec 14, 2007 at 03:39:26PM -0500, Jeff Garzik wrote:
[EMAIL PROTECTED] wrote:
From: Randy Dunlap <[EMAIL PROTECTED]>
...
So I think the breakage that occurs is mitigated by two factors:
1) kernel hackers that do their own configs are expected to be able to
[EMAIL PROTECTED] wrote:
From: Randy Dunlap <[EMAIL PROTECTED]>
Make E1000E default to the same kconfig setting as E1000. So people's
machiens don't stop working when they use oldconfig.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
Cc: Jeff Garzik <[EMAIL PROTECTED]>
Cc
Adrian Bunk wrote:
Code used by the non-__devinit s2io_open() mustn't be __devinit.
This patch fixes the following section mismatch with CONFIG_HOTPLUG=n:
<-- snip -->
...
WARNING: vmlinux.o(.text+0x6f6e3e): Section mismatch: reference to
.init.text.20:s2io_test_intr (between 's2io_open'
Adrian Bunk wrote:
This patch fixes the following section mismatch with CONFIG_HOTPLUG=n:
<-- snip -->
...
WARNING: vmlinux.o(.init.text.20+0x4cb25): Section mismatch: reference to
.exit.text:sis190_mii_remove (between 'sis190_init_one' and 'read_eeprom')
...
<-- snip -->
Signed-off-by:
Adrian Bunk wrote:
This patch fixes the following section mismatch with CONFIG_HOTPLUG=n:
-- snip --
...
WARNING: vmlinux.o(.init.text.20+0x4cb25): Section mismatch: reference to
.exit.text:sis190_mii_remove (between 'sis190_init_one' and 'read_eeprom')
...
-- snip --
Signed-off-by:
[EMAIL PROTECTED] wrote:
From: Randy Dunlap [EMAIL PROTECTED]
Make E1000E default to the same kconfig setting as E1000. So people's
machiens don't stop working when they use oldconfig.
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
Cc: Jeff Garzik [EMAIL PROTECTED]
Cc: Auke Kok [EMAIL
Adrian Bunk wrote:
Code used by the non-__devinit s2io_open() mustn't be __devinit.
This patch fixes the following section mismatch with CONFIG_HOTPLUG=n:
-- snip --
...
WARNING: vmlinux.o(.text+0x6f6e3e): Section mismatch: reference to
.init.text.20:s2io_test_intr (between 's2io_open' and
Adrian Bunk wrote:
On Fri, Dec 14, 2007 at 03:39:26PM -0500, Jeff Garzik wrote:
[EMAIL PROTECTED] wrote:
From: Randy Dunlap [EMAIL PROTECTED]
...
So I think the breakage that occurs is mitigated by two factors:
1) kernel hackers that do their own configs are expected to be able to
figure
Orion Poplawski wrote:
Not sure what the latest status of sata_mv hotplug should be, but it
seems close. I'm currently running 2.6.24-0.81.rc4.git7.fc9 with a
MV88SX5081. Pulled a couple drives and re-added. One device got
re-added, but the other did not. It seems like I got the system to
Orion Poplawski wrote:
Not sure what the latest status of sata_mv hotplug should be, but it
seems close. I'm currently running 2.6.24-0.81.rc4.git7.fc9 with a
MV88SX5081. Pulled a couple drives and re-added. One device got
re-added, but the other did not. It seems like I got the system to
Theodore Tso wrote:
I think the userspace config problems were mainly due to the fact that
there wasn't a single official userspace utility package for the
random number package. Comments in drivers/char/random.c for how to
set up /etc/init.d/random is Just Not Enough.
Absolutely.
If we
Matt Mackall wrote:
On Sat, Dec 08, 2007 at 02:36:33PM -0500, Jeff Garzik wrote:
As an aside...
Speaking as the maintainer rng-tools, which is the home of the hardware
RNG entropy gathering daemon...
I wish somebody (not me) would take rngd and several other projects, and
combine them
As an aside...
Speaking as the maintainer rng-tools, which is the home of the hardware
RNG entropy gathering daemon...
I wish somebody (not me) would take rngd and several other projects, and
combine them into a single actively maintained "entropy gathering" package.
IMO entropy gathering
Theodore Tso wrote:
On Sat, Dec 08, 2007 at 11:33:57AM -0600, Mike McGrath wrote:
Huh? What's the concern? All you are submitting is a list of
hardware devices in your system. That's hardly anything sensitive
We actually had a very vocal minority about all of that which ended up
putting
Theodore Tso wrote:
On Sat, Dec 08, 2007 at 11:33:57AM -0600, Mike McGrath wrote:
Huh? What's the concern? All you are submitting is a list of
hardware devices in your system. That's hardly anything sensitive
We actually had a very vocal minority about all of that which ended up
putting
As an aside...
Speaking as the maintainer rng-tools, which is the home of the hardware
RNG entropy gathering daemon...
I wish somebody (not me) would take rngd and several other projects, and
combine them into a single actively maintained entropy gathering package.
IMO entropy gathering
Matt Mackall wrote:
On Sat, Dec 08, 2007 at 02:36:33PM -0500, Jeff Garzik wrote:
As an aside...
Speaking as the maintainer rng-tools, which is the home of the hardware
RNG entropy gathering daemon...
I wish somebody (not me) would take rngd and several other projects, and
combine them
Theodore Tso wrote:
I think the userspace config problems were mainly due to the fact that
there wasn't a single official userspace utility package for the
random number package. Comments in drivers/char/random.c for how to
set up /etc/init.d/random is Just Not Enough.
Absolutely.
If we
Divy Le Ray wrote:
Jeff Garzik wrote:
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h |1
drivers/net/cxgb3/cxgb3_main
Notable: kill spurious NCQ completion detection
libata disabling command queueing (aka NCQ) based on some hueristics for
detection device brokenness that ultimately turned out to be broken.
Remove the broken hueristic and turn NCQ back on for all the wrongfully
maligned hard drives.
Nothing remarkable. Mainly bonding fixes and bringing ibm_newemac up to
snuff.
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:
Documentation/networking/bonding.txt | 29
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h |1
drivers/net/cxgb3/cxgb3_main.c| 82
drivers/net/cxgb3/cxgb3_offload.c | 15
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Update GPIO mapping for T3C.
Update xgmac for T3C support.
Fix typo in mtu table.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
applied #upstream-fixes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Divy Le Ray wrote:
Jeff Garzik wrote:
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/cxgb3/adapter.h |1
drivers/net/cxgb3/cxgb3_main.c| 82
Nothing remarkable. Mainly bonding fixes and bringing ibm_newemac up to
snuff.
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:
Documentation/networking/bonding.txt | 29
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/cxgb3/adapter.h |1
drivers/net/cxgb3/cxgb3_main.c| 82
drivers/net/cxgb3/cxgb3_offload.c | 15 ++
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Update GPIO mapping for T3C.
Update xgmac for T3C support.
Fix typo in mtu table.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
applied #upstream-fixes
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Notable: kill spurious NCQ completion detection
libata disabling command queueing (aka NCQ) based on some hueristics for
detection device brokenness that ultimately turned out to be broken.
Remove the broken hueristic and turn NCQ back on for all the wrongfully
maligned hard drives.
Tom Lanyon wrote:
Hi list,
Just built a new machine with a Pioneer SATA DVD drive and linux
distro install CDs are not recognising it. The drive is connected to
the ICH9R southbridge of an Intel P35 chipset motherboard.
I can boot from the CD/DVD so the drive itself is working, but the
kernel
Tom Lanyon wrote:
Hi list,
Just built a new machine with a Pioneer SATA DVD drive and linux
distro install CDs are not recognising it. The drive is connected to
the ICH9R southbridge of an Intel P35 chipset motherboard.
I can boot from the CD/DVD so the drive itself is working, but the
kernel
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
on systems with memory located above 4GB. We need to delay setting the 64-bit
DMA mask until the PRD table and padding buffer are allocated so that they don't
get allocated above 4GB and break
Alan Cox wrote:
For things like SATA based devices they aren't that fast yet.
You forget the Gigabyte i-RAM.
For others: the i-RAM is a SATA-based device that plugs into a PCI slot
on your motherboard (for power), providing RAM+battery backup as fast as
your SATA bus and DIMMs will go.
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ahci.c |4
drivers/ata/pata_amd.c |5 +++--
drivers/ata/pata_via.c |4 ++--
drivers/ata/sata_mv.c |
Fixes several ugly bugs...
Please pull from 'upstream-fixes' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-fixes
to receive the following updates:
drivers/net/fec_mpc52xx.c|4 ++--
drivers/net/gianfar.c|2 +-
Vitaly Bordug wrote:
With that patch fixed.c now fully emulates MDIO bus, thus no need
to duplicate PHY layer functionality. That, in turn, drastically
simplifies the code, and drops down line count.
As an additional bonus, now there is no need to register MDIO bus
for each PHY, all emulated
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
revert inavertant file mode changes
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/chelsio/cxgb2.c |0
drivers/net/chelsio/pm3393.c |0
drivers/net/chelsio/sge.c|0
drivers/net/chelsio/sge.h|
ion.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Tested-by: "Thomas Lindroth" <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Cc: Jeff Garzik <[EMAIL PROTECTED]>
Cc: Tejun Heo <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton &l
peerchen wrote:
Add the device IDs of legacy mode of MCP79 AHCI controller to ahci.c
The patch base on kernel 2.6.24-rc3
Signed-off-by: Peer Chen <[EMAIL PROTECTED]>
applied #upstream-fixes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Robert Hancock wrote:
We need to run any DMA command with result taskfile requested in ADMA mode
when the port is in ADMA mode, otherwise it may try to use the legacy DMA engine
in ADMA mode which is not allowed. Enforce this with BUG_ON() since data
corruption could potentially result if this
Nicolas Pitre wrote:
On Mon, 3 Dec 2007, Linus Torvalds wrote:
That said, none of the changes are really _exciting_ or really scary. And
we should have fixed a number of regressions, although more certainly
remain.
Any reason for this:
mode change 100644 => 100755
Nicolas Pitre wrote:
On Mon, 3 Dec 2007, Linus Torvalds wrote:
That said, none of the changes are really _exciting_ or really scary. And
we should have fixed a number of regressions, although more certainly
remain.
Any reason for this:
mode change 100644 = 100755
Robert Hancock wrote:
We need to run any DMA command with result taskfile requested in ADMA mode
when the port is in ADMA mode, otherwise it may try to use the legacy DMA engine
in ADMA mode which is not allowed. Enforce this with BUG_ON() since data
corruption could potentially result if this
peerchen wrote:
Add the device IDs of legacy mode of MCP79 AHCI controller to ahci.c
The patch base on kernel 2.6.24-rc3
Signed-off-by: Peer Chen [EMAIL PROTECTED]
applied #upstream-fixes
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
-by: Thomas Lindroth [EMAIL PROTECTED]
Acked-by: Alan Cox [EMAIL PROTECTED]
Cc: Jeff Garzik [EMAIL PROTECTED]
Cc: Tejun Heo [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
applied #upstream-fixes
--
To unsubscribe from this list
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
revert inavertant file mode changes
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/chelsio/cxgb2.c |0
drivers/net/chelsio/pm3393.c |0
drivers/net/chelsio/sge.c|0
drivers/net/chelsio/sge.h|0
Vitaly Bordug wrote:
With that patch fixed.c now fully emulates MDIO bus, thus no need
to duplicate PHY layer functionality. That, in turn, drastically
simplifies the code, and drops down line count.
As an additional bonus, now there is no need to register MDIO bus
for each PHY, all emulated
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ahci.c |4
drivers/ata/pata_amd.c |5 +++--
drivers/ata/pata_via.c |4 ++--
drivers/ata/sata_mv.c |
Fixes several ugly bugs...
Please pull from 'upstream-fixes' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-fixes
to receive the following updates:
drivers/net/fec_mpc52xx.c|4 ++--
drivers/net/gianfar.c|2 +-
Alan Cox wrote:
For things like SATA based devices they aren't that fast yet.
You forget the Gigabyte i-RAM.
For others: the i-RAM is a SATA-based device that plugs into a PCI slot
on your motherboard (for power), providing RAM+battery backup as fast as
your SATA bus and DIMMs will go.
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
on systems with memory located above 4GB. We need to delay setting the 64-bit
DMA mask until the PRD table and padding buffer are allocated so that they don't
get allocated above 4GB and break
Neil Brown wrote:
I've been looking at use BIO_RW_FAILFAST in md/raid to improve
handling of some error cases.
This is particularly significant for the DASD driver (s390 specific).
I believe it uses optic fibre to connect to the drives. When one of
these paths is unplugged, IO requests will
Neil Brown wrote:
I've been looking at use BIO_RW_FAILFAST in md/raid to improve
handling of some error cases.
This is particularly significant for the DASD driver (s390 specific).
I believe it uses optic fibre to connect to the drives. When one of
these paths is unplugged, IO requests will
ot;Thomas Lindroth" <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Cc: Jeff Garzik <[EMAIL PROTECTED]>
Cc: Tejun Heo <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Mark Lord wrote:
Mark Lord wrote:
Mark Lord wrote:
I've only just recently tried running 2.6.24 on my main machine.
And it appears that I'll have to go back to 2.6.23,
because the USB mouse is not working correctly.
Single-clicking on things with 2.6.24 very frequently gives a
Mark Lord wrote:
Mark Lord wrote:
Mark Lord wrote:
I've only just recently tried running 2.6.24 on my main machine.
And it appears that I'll have to go back to 2.6.23,
because the USB mouse is not working correctly.
Single-clicking on things with 2.6.24 very frequently gives a
double-click.
]
Acked-by: Alan Cox [EMAIL PROTECTED]
Cc: Jeff Garzik [EMAIL PROTECTED]
Cc: Tejun Heo [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
I'll add this to the queue. Sorry for missing it.
Jeff
--
To unsubscribe
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ata_piix.c| 28 +++
drivers/ata/libata-core.c |8 +++--
drivers/ata/libata-eh.c | 42
Kristen Carlson Accardi wrote:
Enclosure Management via LED
This patch implements Enclosure Management via the LED protocol as specified
in AHCI specification.
Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]>
---
This revision makes the change to the comment requested by Mark Lord,
Alan Cox wrote:
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos <[EMAIL PROTECTED]> wrote:
Can you stick a stack trace in at that point ? That would help diagnose
it a great deal quicker.
Finally done - found out hard way that BUG() is too bad and
dump_st5ack() suits me better.
Thanks.
sonic zhang wrote:
UDMA Mode - Frequency compatibility
UDMA5 - 100 MB/s - SCLK = 133 MHz
UDMA4 - 66 MB/s- SCLK >= 80 MHz
UDMA3 - 44.4 MB/s - SCLK >= 50 MHz
UDMA2 - 33 MB/s- SCLK >= 40 MHz
Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]>
---
drivers/ata/pata_bf54x.c |7
Vitaly Bordug wrote:
With that patch fixed.c now fully emulates MDIO bus, thus no need
to duplicate PHY layer functionality. That, in turn, drastically
simplifies the code, and drops down line count.
As an additional bonus, now there is no need to register MDIO bus
for each PHY, all emulated
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
The patch ensures that a GSO skb has enough headroom
to push an encapsulating cpl_tx_pkt_lso header.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
applied 1-3
--
To unsubscribe from this list: send the line "unsubscribe
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
The patch ensures that a GSO skb has enough headroom
to push an encapsulating cpl_tx_pkt_lso header.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
applied 1-3
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
Vitaly Bordug wrote:
With that patch fixed.c now fully emulates MDIO bus, thus no need
to duplicate PHY layer functionality. That, in turn, drastically
simplifies the code, and drops down line count.
As an additional bonus, now there is no need to register MDIO bus
for each PHY, all emulated
sonic zhang wrote:
UDMA Mode - Frequency compatibility
UDMA5 - 100 MB/s - SCLK = 133 MHz
UDMA4 - 66 MB/s- SCLK = 80 MHz
UDMA3 - 44.4 MB/s - SCLK = 50 MHz
UDMA2 - 33 MB/s- SCLK = 40 MHz
Signed-off-by: Sonic Zhang [EMAIL PROTECTED]
---
drivers/ata/pata_bf54x.c |7 +++
1
Alan Cox wrote:
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos [EMAIL PROTECTED] wrote:
Can you stick a stack trace in at that point ? That would help diagnose
it a great deal quicker.
Finally done - found out hard way that BUG() is too bad and
dump_st5ack() suits me better.
Thanks.
Kristen Carlson Accardi wrote:
Enclosure Management via LED
This patch implements Enclosure Management via the LED protocol as specified
in AHCI specification.
Signed-off-by: Kristen Carlson Accardi [EMAIL PROTECTED]
---
This revision makes the change to the comment requested by Mark Lord,
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ata_piix.c| 28 +++
drivers/ata/libata-core.c |8 +++--
drivers/ata/libata-eh.c | 42
David Sterba wrote:
Hi,
I'm submitting driver for IPWireless PC Card, used for 4G
internet connection.
The driver has been in -mm series as ipwireless_cs.git tree for
some time, is actively used and there are currently no
outstanding bugs.
I'd like to let the driver pass through LKML and then
David Sterba wrote:
Hi,
I'm submitting driver for IPWireless PC Card, used for 4G
internet connection.
The driver has been in -mm series as ipwireless_cs.git tree for
some time, is actively used and there are currently no
outstanding bugs.
I'd like to let the driver pass through LKML and then
Tejun Heo wrote:
2. Filter out certain commands from ACPI. I definitely don't like BIOS
locking up random features via _GTF commands. It makes debugging difficult.
I agree.
Take a look at what Alan has been doing for the "trusted" command stuff.
At the very least we should definitely blare
Tejun Heo wrote:
2. Filter out certain commands from ACPI. I definitely don't like BIOS
locking up random features via _GTF commands. It makes debugging difficult.
I agree.
Take a look at what Alan has been doing for the trusted command stuff.
At the very least we should definitely blare a
ATA_HORKAGE_STUCK_ERR for ATAPI tape drives
Gabriel C (1):
pata_sis.c: Add Packard Bell EasyNote K5305 to laptops
Jeff Garzik (1):
pata_ali: trim trailing whitespace (fix checkpatch complaints)
Mark Lord (1):
libata-scsi: be tolerant of 12-byte ATAPI commands in 16-byte CDBs
|2 +-
include/linux/pci_ids.h|4
16 files changed, 84 insertions(+), 61 deletions(-)
Ayaz Abdulla (2):
forcedeth: new mcp79 pci ids
forcedeth boot delay fix
Benjamin Herrenschmidt (1):
ibm_newemac: Fix possible lockup on close
Jeff Garzik (1):
dmfe
sonic zhang wrote:
INT status can be OR.
Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]>
---
drivers/ata/pata_bf54x.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
applied
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
sonic zhang wrote:
INT status can be OR.
Signed-off-by: Sonic Zhang [EMAIL PROTECTED]
---
drivers/ata/pata_bf54x.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
applied
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
701 - 800 of 7471 matches
Mail list logo
