On Wed, 30 Jan 2008 17:45:48 +0100
Nicolas Ferre <[EMAIL PROTECTED]> wrote:
> From: Marc Pignat <[EMAIL PROTECTED]>
>
> MMC_POWER_ON is a noop, no need to set the power pin again.
>
> Signed-off-by: Marc Pignat <[EMAIL PROTECTED]>
> Signed-off-by: Nicolas Ferre <[EMAIL PROTECTED]>
> ---
Perhaps
detect_pin >= 0) {
> + free_irq(gpio_to_irq(host->detect_pin),host->mmc);
> + cancel_delayed_work(&host->mmc->detect);
I also pointed this out. mmc_remove_host() will synchronize this for
you.
--
-- Pierre Ossman
Linux kernel, MMC
d just creating another vt with "chvt 2", but that is insufficient to
trigger the bug.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http
On Mon, 18 Feb 2008 20:50:01 +0100
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> On Monday, 18 of February 2008, Pierre Ossman wrote:
> > The patch "[RTNETLINK]: Send a single notification on device state
> > changes." kills (at least)
> > the
On Mon, 18 Feb 2008 21:50:12 +0100
Pierre Ossman <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Feb 2008 20:50:01 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > On Monday, 18 of February 2008, Pierre Ossman wrote:
> > > The patch "[RTN
Lenovo and a HP laptop here.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
--
To unsubscribe from this list: send the line "unsubscr
On Tue, 19 Feb 2008 12:55:13 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Pierre Ossman wrote:
> >
> > Anyone else seeing these problems? Someone should as I've seen the problem
> > on both a Lenovo and a HP laptop here.
>
>
> I'm definitely se
ings confused. What it checks is if the mmc bus
handler (not a proper driver model, just a way of separating the MMC, SD and
SDIO stuff) has a resume function. And if it doesn't, it removes the card
(since it cannot revive it at resume).
So the only thing I can think of is to delay the remo
the asymmetric case, I guess that would do. But I still want to remove
devices when the bus handler has no suspend handling.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core de
On Mon, 4 Feb 2008 19:25:42 +0100
Frank Seidel <[EMAIL PROTECTED]> wrote:
> From: Frank Seidel <[EMAIL PROTECTED]>
>
> This patch (base on current linus git tree plus Philip Langdales
> suspend/resume patch) adds support for the Ricoh RL5c476 chip:
> with this the mmc adapter that needs this disa
try adding some printk() to pxamci's data transfer routines
and dump the data when it is fresh.
>
> I'd advise at least adding dumping the raw_scr values
> in the SCR version error to be able to track such error postings better
> in the future.
>
It's definitely some
On Thu, 7 Feb 2008 09:20:38 +0100
Frank Seidel <[EMAIL PROTECTED]> wrote:
> >
> > Wouldn't it be prudent to have a check that this is indeed a R5C832,
> > and a failure mode if it's none of the two known devices?
>
> Also thought about that, but as far as i can see this cannot happen since
> we
ion of
the timeout, or you have a hardware bug. And to determine that we need to check
what is actually going over the wire. As you've checked the data contents, that
isn't the problem. So the only remaining thing is checking the timing.
Rgds
--
-- Pierre Ossman
Linux kerne
> + goto err_remove_host;
> + }
> +
> + if (slot->pdata->get_ro != NULL) {
> + r = device_create_file(&mmc->class_dev,
> + &dev_attr_ro);
> + }
> +
You have a bit of a race her
;[EMAIL PROTECTED]>
> Signed-off-by: Nicolas Ferre <[EMAIL PROTECTED]>
> ---
Applied thanks.
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rde
r <[EMAIL PROTECTED]>
> Signed-off-by: Tony Lindgren <[EMAIL PROTECTED]>
> ---
NAK. This header should not be needed in host drivers. It's a clear sign you're
doing something bad.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp:/
On Mon, 3 Dec 2007 14:39:26 +
Ben Dooks <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 03, 2007 at 08:22:07AM -0600, Matt Porter wrote:
> >
> > What's the status of Ben's separation patches? I haven't seen a posting of
> > those
> > versus a recent kernel. I've got some SDHCI driver glue for the n
index for multi controllers case
Frank Seidel (1):
mmc: extend ricoh_mmc to support Ricoh RL5c476
Philip Langdale (1):
mmc: Handle suspend/resume in Ricoh MMC disabler
Pierre Ossman (2):
mmc: remove sdhci and mmc_spi experimental markers
MAINTAINERS: remove non-existant
have access to the data structures long enough to output
data.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
--
To unsubscribe from this list: send
On Thu, 21 Feb 2008 19:46:20 +0100
Haavard Skinnemoen <[EMAIL PROTECTED]> wrote:
>
> When the card is reinserted, the MMC core will try to send a
> SEND_STATUS command again. This time, the card won't respond because it
> is in the "idle" state, and the MMC core will think the card is gone.
>
>
d code.
>
I'm not too familiar with that driver, but they've been playing around
with multiplexing several cards into one controller. Might be bits and
pieces of that.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core deve
On Mon, 25 Feb 2008 12:58:30 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> Thanks for the explanations.
>
> On Mon, 25 Feb 2008, Pierre Ossman wrote:
>
> > Trying to keep up with the PM changes is a full time job. For now I've
> > mostly ignored it as I
Version increase of the wbsd driver.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
Even though the changes are minor for the next release an increasing
version number simplifies my support issues.
Index: linux/drivers/mmc/
Remove lots of trailing whitespace caused by not-so-great editor.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
--- linux/drivers/mmc/wbsd.c.orig 2005-07-11 14:26:40.0 +0200
+++ linux/drivers/mmc/wbsd.c 2005-07-11 14:27:02.0 +0200
@@ -93,7 +93,7 @@
static inlin
Create a mmc_host class to allow enumeration of MMC host controllers
even though they have no card(s) inserted.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
(This will also allow cards to be enumerated by being able to find the
hosts.)
Index: linux-wbsd/drivers/mmc
Russell King wrote:
>No no no no no. Repeat after me ten times. Empty or non-existant release
>functions are bad and cause oopsen. I will not create code which does
>this.
>
>
Sorry. I thought it was a generic cleanup function and since nothing was
allocated in the register function I didn't
Russell King wrote:
>The allocation function should initialise class_dev as much as possible.
>The registration function should add the class device with the class
>model. The unregistration should remove the class device from the class
>model, but _not_ free it. The free function should drop th
Russell King wrote:
>On Fri, Jul 15, 2005 at 10:21:43PM +0200, Pierre Ossman wrote:
>
>
>>Russell King wrote:
>>
>>
>>>Also note that since we have a class_dev, the mmc_host 'dev' field can
>>>be removed. However, we'll probably
Sorry about reporting this error so late but the machine in question had
gone some time without upgrades.
The problem I'm seeing is that IRQs stop working for one of the IRQ
slots on the machine. It's only that slot, not the entire IRQ, since the
two slots (it's a small machine) both get routed to
Pierre Ossman wrote:
> ** PCI interrupts are no longer routed automatically. If this
> ** causes a device to stop working, it is probably because the
> ** driver failed to call pci_enable_device(). As a temporary
> ** workaround, the "pci=routeirq" argument restores the
Jesper Juhl wrote:
>
>Have you tried the suggestion given "... As a temporary workaround,
>the "pci=routeirq" argument..." ?
>You could also try the pci=noacpi boot option to see if that changes anything.
>
>
No, I missed that one. The machine works fine with either of those two
options. I sent
Richard Purdie wrote:
> This fixes what looks like a bit/byte counting error in the MMC/SD code
> which was causing data corruption (in the -mm tree).
>
> Signed-off-by: Richard Purdie <[EMAIL PROTECTED]>
Ooops... Must have been late in the evening. Sorry about that blunder.
Rgds
Pierre
-
To uns
Russell King wrote:
>
>I still don't like the needless duplication. How about doing it this
>way (see the attached patch.)
>
>Note: I also intend to move MMC over to using an IDR for the host
>numbers, which is why we need to setup the name at registration
>time, not allocation time.
>
>
>
Thi
Pierre Ossman wrote:
> Pierre Ossman wrote:
>
>>I'm having problem with the interrupt getting killed after suspend with
>>my 8139cp controller. The problem only appears if the cable is connected
>>during resume (before suspend is irrelevant) and the interface is do
side-effects found.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
---
Previously submitted: 2005-03-16
Previously submitted: 2004-12-03
Index: linux-wbsd/drivers/mmc/mmc_block.c
===
--- linux-wbsd/drivers/mmc/mmc_block.c (re
Jörn Engel wrote:
>Question came up before, albeit with a different phrasing. One
>possible approach to benefit from this ability would be to create a
>"forget" operation. When a filesystem already knows that some data is
>unneeded (after a truncate or erase operation), it will ask the device
>t
Jörn Engel wrote:
>On Tue, 16 August 2005 20:13:36 +0200, Jörn Engel wrote:
>
>
>>Yes. Most filesystems expect to find either 1) old data or 2) new
>>data. Blocks full of 0xff are non-expected.
>>
>>
>
>Maybe this isn't obvious. Because of this expectation, it is
>absolutely not safe to p
randy_dunlap wrote:
>+The DMA:able address space is the lowest 16 MB of _physical_ memory.
> The DMA-able
>+Also the transfer block may not cross page boundaries (which are 64k).
> I would write:(which are 64 KB).
>
>if I knew that was correct, but I don't.
Documentation for how the ISA DMA controller is handled in the kernel.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
New version after feedback from Randy Dunlap.
Index: linux-wbsd/Documentation/DMA-ISA-LPC.txt
===
---
I upgraded a machine from 2.6.11.7 to 2.6.12.2 today and the only thanks
I got was a brand new kernel panic. From the backtrace it seems that the
dc395x driver is the culprit. From what I can tell it hasn't undergone
any changes between the two versions.
Image of kernel panic:
http://craffe.se/im
John W. Linville wrote:
>On Mon, Jul 04, 2005 at 12:22:53AM +0200, Pierre Ossman wrote:
>
>
>>After suspend the driver needs to retest link status in case the cable
>>has been inserted or removed during the suspend.
>>
>>Signed-off-by: Pierre Ossman <[EMAIL
Pierre Ossman wrote:
> I'm having problem with the interrupt getting killed after suspend with
> my 8139cp controller. The problem only appears if the cable is connected
> during resume (before suspend is irrelevant) and the interface is down.
>
> Both suspend-to-disk and su
Andrew Morton wrote:
>The fact that this is enabled under the experimental
>CONFIG_MMC_BULKTRANSFER seems unfortunate. I mean, if the code works OK
>then we should just enable it unconditionally, no?
>
>
>
It was made this way to make Russell more open to it. I have since not
recieved any more
Russell King wrote:
>
>I'd rather not. The problem is that we have a host (thanks Intel)
>which is unable to report how many bytes were transferred before an
>error occurs. My fear is that doing anything other than sector by
>sector write will lead to corruption should an error occur.
>
>However
Russell King wrote:
>On Thu, Aug 18, 2005 at 09:26:03AM +0200, Pierre Ossman wrote:
>
>
>>We had this discussion on LKML and Alan Cox' comment on it was that a
>>solution like this would be acceptable, where we try and shove
>>everything out first and then
Alan Cox wrote:
>On Iau, 2005-08-18 at 09:26 +0200, Pierre Ossman wrote:
>
>
>>everything out first and then fall back on sector-by-sector to determine
>>where an error occurs. This will only break if the problematic sector
>>keeps shifting around, but at that point
Pavel Machek wrote:
>>* Transport problem. The driver will report back a CRC error, timeout or
>>whatnot and break. We might not know how many sectors survived so we try
>>again, going sector-by-sector. We might get a transfer error again,
>>possibly even before the previous one. But at this point
Russell King wrote:
>
>Hmm, I think I've gone back to preferring something similar to your
>original approach actually. I've also included the IDR patch.
>
>
>
Ok. Just as long as it works. :)
My two concerns are:
* Things that assume there's a name for every kobject.
* Things that assume th
Pavel Machek wrote:
>
>Maybe the card is pretty close to going to crash, but... two disk
>successive disk errors still should not be cause for journal
>corruption.
>
>[Also errors could be corelated. Imagine severe overheat. You'll
>successive failing writes, but if you let cool it down, you'll st
Adrian Bunk wrote:
> [ this time with a better subject ]
>
> "extern inline" doesn't make sense.
>
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
Isn't 'extern inline' an old gcc trick to force inlining? (instead of
just hinting)
-
To unsubscribe from this list: send the line "unsubscrib
Adds a new ios for setting the chip select pin on MMC cards. Needed on
SD controllers which use this pin for other things and therefore cannot
have it pulled high at all times.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
Index: linux/drivers/mmc
Use the chip select ios in the wbsd driver.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
Index: linux/drivers/mmc/wbsd.c
===
--- linux/drivers/mmc/wbsd.c (revision 161)
+++ linux/drivers/mmc/wbsd.c (working copy)
@@ -42,7
Only show the scr file in sysfs for SD cards. Previously this was
present for all cards but had a contents of 0 for MMC cards.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
Index: linux-wbsd/drivers/mmc/mmc_sysfs.c
===
---
Meelis Roos wrote:
>
> It's OK then - I'm not using any suspend and I had a problem that my
> machine powered down instead of reboot. The patch that went into 2.6.13
> after rc7 fixed it for me. So the current tree is OK for me and if it's
> OK for you too after suspend2 changes then this case can
Eric W. Biederman wrote:
>Hmm. Looking at that bug report it specifies 2.6.11. Does this
>problem really happen in 2.6.13?
>
>
>
I first noticed it in 2.6.11. It was fixed sometime during 2.6.13-rc
only to be killed of again in 2.6.13-rc7. The bugzilla now has a patch
for 2.6.13 which fixes t
Eric W. Biederman wrote:
>Thanks.
>
>This is clearly a code path I missed when I was fixing things.
>
>When I made the final acpi change I checked for any other users
>of device_suspend and it seems I was blind and missed this one.
>Looking again...
>
>The patch in the bug report looks correct. H
Register interrupt handler when net device is registered. Avoids missing
interrupts if the interrupt mask gets out of sync.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
---
The reason this patch is needed for me is that the resume function is
broken. It enables interrupts unconditi
Jeff Garzik wrote:
>
> Where is CONFIG_PM?
>
> Jeff
I'm not sure you're receiving my mails, but I'll give it a try anyway.
It would also seem that my MTA is choking on your MX entries. I'll look
into that once I get home.
CONFIG_PM is missing because of consistency with i8259.c, on which th
It would seem that swsusp doesn't properly suspend devices, or more
precisely it wakes them up again before suspending the machine.
The problem is in swsusp_suspend(). It is designed as if
swsusp_arch_suspend() would suspend the hardware, when in fact all it
does is prepare for a suspend. The effe
Rafael J. Wysocki wrote:
>On Wednesday, 7 of September 2005 13:20, Pierre Ossman wrote:
>
>
>>It would seem that swsusp doesn't properly suspend devices, or more
>>precisely it wakes them up again before suspending the machine.
>>
>>
>
>Yes, it d
On Sat, 29 Dec 2007 00:11:42 -0800
Philip Langdale <[EMAIL PROTECTED]> wrote:
> As pci config space is reinitialised on a suspend/resume cycle, the
> disabler needs to work its magic at resume time. For symmetry this
> change also explicitly enables the controller at suspend time but
> it's not st
Could you elaborate why the
controller won't work with MMC cards? I haven't seen any differences from SD.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer
On Sun, 6 Jan 2008 20:02:46 -0800
"raki john" <[EMAIL PROTECTED]> wrote:
>
> Can I replace drivers/mmc directory in 2.6.22.1 with drivers/mmc
> directory in 2.6.23.1. Does this cause any issues. Is there any code
> in drivers/mmc in 2.6.23.1 which depends on other features in kernel
> 2.6.23.1.
On Mon, 7 Jan 2008 15:31:32 -0800
"raki john" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Please CC me on responses.
>
> I am working on a SD/MMC Host driver .
>
> I am getting kerenl oops after mmc_register_card () is called.
> i working on LINUX 2.6.22.1 kerenl.
>
> What might be the reason fo
e must me "vendor will guarantee it works". And that is
not the kind of "support" that needs a distinction in the code.
So, again, if you feel that there is a hardware difference between 4-bit MMC
and 4-bit SD then please elaborate as it is my understanding that they are
identic
at's just iterating what's already been said. My claim is that 4-bit is
4-bit, regardless if it's MMC or SD. So if you want this patch to go in you
need to explain why there is a difference for the blackfin controller.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer
On Tue, 8 Jan 2008 16:44:08 -0500
"Mike Frysinger" <[EMAIL PROTECTED]> wrote:
> On Jan 8, 2008 3:49 PM, Pierre Ossman <[EMAIL PROTECTED]> wrote:
> > So, again, if you feel that there is a hardware difference between 4-bit
> > MMC and 4-bit SD then please ela
erring to. The
MMC layer supports legacy cards, SDHC and MMC 4.2 addressing. All addresses are
32-bit.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://
this work with 2.6.23?
Please enable CONFIG_MMC_DEBUG and include a copy of the output of dmesg.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdes
e this:
_If_ it truly cannot handle 4-bit MMC, then Mike's patch is the way to go. But
I'm not yet convinced that the problem is related to MMC vs SD.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pu
n how it progresses. I'd like an at least plausible
explanation, preferably also some empirical data, before I'm ready to accept
Mike's patch.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://p
On Sun, 2 Dec 2007 12:22:31 +0100 (CET)
Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
>
> I gave it a try:
> - Remove existing alignment attributes from some device_id types
> - Introduce kernel_* types with proper size and alignment for
> cross-compilation (sample for m68k included)
>
On Sat, 8 Dec 2007 22:58:11 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 03, 2007 at 09:02:19PM +1100, Rusty Russell wrote:
> > So, just insert two bits of padding in sdio_device_id and insert a comment
> > saying "/* Explicit padding: works even if we're cross-compiling */".
>
> W
On Thu, 06 Dec 2007 23:12:46 -0500 (EST)
Nicolas Pitre <[EMAIL PROTECTED]> wrote:
> This field and corresponding defines are simply never used anywhere
> in the code. But its mere presence is enough to confuse some host
> driver authors who attempt to rely on it. Let's eliminate the
> possibil
On Mon, 10 Dec 2007 19:11:12 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 09, 2007 at 06:08:18PM +0100, Pierre Ossman wrote:
> >
> > This still requires a bit of maintenance to set up a kerneltypes.h for
> > every arch.
>
> Better doing this wor
---
include/linux/pci_ids.h |1 +
4 files changed, 61 insertions(+), 10 deletions(-)
Nicolas Pitre (1):
mmc: remove unused 'mode' from the mmc_host structure
Pierre Ossman (4):
sdhci: describe quirks
sdhci: don't warn about sdhci 2.0 controllers
sdhci: use PIO
that Windows only stops a device to rebalance hardware
> resources.
>
> Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
>
Tested-by: Pierre Ossman <[EMAIL PROTECTED]>
No noticeable issues with suspend or hibernate using this patch.
Rgds
Pierre
signature.asc
Description: PGP signature
;
It wasn't wrong the last time you brought this up, and it still isn't wrong.
Those bits aren't defined until version 1.2 of the EXT_CSD register, hence we
do not trust them. If you have some broken card that you feel you must have
support for, then start working on some quirks s
certain
workarounds to specific cards. Then add some bit saying "is really EXT_CSD 1.2"
and check for that bit when parsing the EXT_CSD.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.or
On Tue, 02 Oct 2007 17:14:34 +1000
Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> Hrm... allright, tho having this "disabler" driver is butt ugly
> too ... especially since it needs to whack registers in another
> function, that's really quirkland :-)
>
Well, that issue would remain even
edhat.com/show_bug.cgi?id=241348
[2] http://marc.info/?l=linux-nfs&m=118701088726477&w=2
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.r
On Wed, 3 Oct 2007 23:16:59 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <[EMAIL PROTECTED]> wrote:
>
> > OOPS followed by a 3 minute timeout, then completion of boot.
> > Not seen if card (Kingston microSD adapter) is ejected; not seen in
> > 2.6
On Thu, 4 Oct 2007 09:25:15 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> It looks like missing init of the sg list in mmc, does this work?
>
Huh? Isn't the block layer supposed to fill in the entire thing? (i.e.
current contents shouldn't matter)
Rgds
Pierre
signature.asc
Description: PGP
On Thu, 4 Oct 2007 10:06:32 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > Huh? Isn't the block layer supposed to fill in the entire thing?
> > (i.e. current contents shouldn't matter)
>
> Yeah, but sg
On Thu, 4 Oct 2007 12:38:05 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > Is that a yes or a no? You said that the ->page field was involved
> > in
>
> It's a conditional yes, re-read it :-)
>
On Thu, 4 Oct 2007 11:30:14 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > I assume sg_init_one() still can work on an uninitialized sg entry?
>
> Yes, but only if that sg entry is not part of a chained list.
>
I
On Thu, 04 Oct 2007 09:19:40 -0700
Don Mullis <[EMAIL PROTECTED]> wrote:
> This patch fixes the boot.
>
Fantastic. Then will try to get this upstream then.
> >
> > It looks like missing init of the sg list in mmc, does this work?
> >
Jens, is this zeroing needed for each invocation, or reall
On Thu, 04 Oct 2007 10:00:50 -0400
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-10-04 at 08:52 +0200, Pierre Ossman wrote:
> > On Wed, 03 Oct 2007 19:41:16 -0400
> > Trond Myklebust <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > We a
On Thu, 4 Oct 2007 18:42:25 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> diff --git a/drivers/mmc/card/queue.c b/drivers/mmc/card/queue.c
> index b0abc7d..a5d0354 100644
> --- a/drivers/mmc/card/queue.c
> +++ b/drivers/mmc/card/queue.c
Acked-by: Pierre Ossman <[EMAI
g and it is time for them to do so.
>
Print a warning or something so that they can be found. Don't go
breaking systems left and right. People have better things to do than
to fix the build systems for ever program they use.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer
On Fri, 05 Oct 2007 13:36:19 -0400
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-10-05 at 08:25 +0200, Pierre Ossman wrote:
>
> > Print a warning or something so that they can be found. Don't go
> > breaking systems left and right. People have better thi
On Wed, 10 Oct 2007 14:45:40 +0400
Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> ["if (!x & y)" patch from [EMAIL PROTECTED]
> ["if (!x & y)" patch from [EMAIL PROTECTED]
> ["if (!x & y)" patches from [EMAIL PROTECTED]
>
> While we're at it, below is somewhat ugly sparse patch for detecting
> "&&
pport arbitrary block size
Pavel Pisa (1):
arm: i.MX/MX1 SDHC implements SD cards read-only switch read-back
Philip Langdale (1):
mmc: Disabler for Ricoh MMC controller
Pierre Ossman (32):
mmc: remove custom error codes
mmc: improve error code feedback
mmc: read
have a look at it and reping you when I've
solved it.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
-
To unsubscribe from this list: s
On Sun, 23 Dec 2007 23:25:26 -0800
"raki john" <[EMAIL PROTECTED]> wrote:
>
> Does mmc_requeest->stop is equal to mmc_request->data->stop ?
>
> Does mmc_request is equal to mmc_request->data->mrq ?
>
> Does mmc_request->data is equal to mmc_request->cmd->data ?
>
> Does mmc_request
On Wed, 26 Dec 2007 10:40:22 -0800
"raki john" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I am working with pxamci driver(2.6.22.1). I have made , core and host
> as separate modules.
>
> what is the correct order of loading the modules
>
> i am doing in this order first core (mmc_core.ko), then
, UART_IER, port->ier);
}
-static void sdio_uart_receive_chars(struct sdio_uart_port *port, int *status)
+static void sdio_uart_receive_chars(struct sdio_uart_port *port, unsigned int
*status)
{
struct tty_struct *tty = port->tty;
unsigned int ch, flag;
--
--
isapnp: No Plug & Play device found
Any ideas on how I can work around this? I'm rather unproductive when I can't
build working kernels.. :/
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer http://p
On Sat, 1 Dec 2007 15:42:23 +0100
Pierre Ossman <[EMAIL PROTECTED]> wrote:
> The latest GCC in Fedora rawhide contains some serious bug (or provokes a
> latent one in the kernel) that makes every kernel built unbootable. It just
> locks up halfway through the init. Kernels
ou get to keep a down-rev
> virtual machine to do it right :-(
>
Nah. The previous gcc package is the one shipped with Fedora 8. So I could just
grab that one (plus cpp and libgomp) and downgrade.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.o
1 - 100 of 486 matches
Mail list logo
