majordomo info at http://vger.kernel.org/majordomo-info.html
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
with these two and an ov2640 fix.
Thanks
Guennadi
/* At this point client .probe() should have run already */
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Tue, 11 Sep 2012, Arnd Bergmann wrote:
> On Tuesday 11 September 2012, Guennadi Liakhovetski wrote:
> > Hi Arnd
> >
> > It probably wouldn't be very difficult to also include
> > arch/arm/plat-mxc/include/mach/ipu.h in this your patch, but you can also
> >
Hi Arnd
It probably wouldn't be very difficult to also include
arch/arm/plat-mxc/include/mach/ipu.h in this your patch, but you can also
leave it for later. Just to make sure it's not something that would make
your future patching more complicated.
Thanks
Guennadi
---
Guennadi Liakhovetski
Hi Arnd
It probably wouldn't be very difficult to also include
arch/arm/plat-mxc/include/mach/ipu.h in this your patch, but you can also
leave it for later. Just to make sure it's not something that would make
your future patching more complicated.
Thanks
Guennadi
---
Guennadi Liakhovetski
On Tue, 11 Sep 2012, Arnd Bergmann wrote:
On Tuesday 11 September 2012, Guennadi Liakhovetski wrote:
Hi Arnd
It probably wouldn't be very difficult to also include
arch/arm/plat-mxc/include/mach/ipu.h in this your patch, but you can also
leave it for later. Just to make sure it's
Denis Efremov
Acked-by: Guennadi Liakhovetski
Note: I didn't test this. I still have a dc390 card in my PC, so, I could
test it, but I haven't yet got time for this and I'll be away the next
week. The patch looks correct and safe. If it does break anything, well,
we'll get to know about that soone
Acked-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
Note: I didn't test this. I still have a dc390 card in my PC, so, I could
test it, but I haven't yet got time for this and I'll be away the next
week. The patch looks correct and safe. If it does break anything, well,
we'll get to know
_Status ! */
> @@ -736,7 +737,7 @@ DC390_Interrupt(void *dev_id)
> }
>
> unlock:
> -spin_unlock_irq(pACB->pScsiHost->host_lock);
> +spin_unlock_irqrestore(pACB->pScsiHost->host_lock, flags);
> return IRQ_HANDLED;
> }
>
> --
&
-host_lock);
+spin_unlock_irqrestore(pACB-pScsiHost-host_lock, flags);
return IRQ_HANDLED;
}
--
1.7.7
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
The recent shdma driver split has mistakenly removed support for partial
DMA transfer size calculation on forced termination. This patch restores
it.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma-base.c |9 +
drivers/dma/sh/shdma.c | 12
include
A recent commit:
commit d6fa5a4e7ab605370fd6c982782f84ef2e6660e7
Author: Guennadi Liakhovetski
serial: sh-sci: prepare for conversion to the shdma base library
is not sufficient to update the sh-sci driver to the new shdma driver
layout. This caused compilation breakage, when
Hi all
as has been reported in this
http://thread.gmane.org/gmane.linux.kernel/1294256/focus=16001
thread, currently sh-sci doesn't comiple in the mainline and in -next if
CONFIG_SERIAL_SH_SCI_DMA is enabled. This patch series fixes this
breakage.
Thanks
Guennadi
---
Guennadi Liakhovetski
Hi all
as has been reported in this
http://thread.gmane.org/gmane.linux.kernel/1294256/focus=16001
thread, currently sh-sci doesn't comiple in the mainline and in -next if
CONFIG_SERIAL_SH_SCI_DMA is enabled. This patch series fixes this
breakage.
Thanks
Guennadi
---
Guennadi Liakhovetski
A recent commit:
commit d6fa5a4e7ab605370fd6c982782f84ef2e6660e7
Author: Guennadi Liakhovetski g.liakhovet...@gmx.de
serial: sh-sci: prepare for conversion to the shdma base library
is not sufficient to update the sh-sci driver to the new shdma driver
layout. This caused compilation breakage
The recent shdma driver split has mistakenly removed support for partial
DMA transfer size calculation on forced termination. This patch restores
it.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
drivers/dma/sh/shdma-base.c |9 +
drivers/dma/sh/shdma.c | 12
On Thu, 26 Jul 2012, Vinod Koul wrote:
> On Thu, 2012-07-26 at 15:58 +0900, Paul Mundt wrote:
> > On Thu, Jul 26, 2012 at 12:19:21PM +0530, Vinod Koul wrote:
> > > On Wed, 2012-07-25 at 12:59 +0900, Paul Mundt wrote:
> > > > On Wed, May 09, 2012 at 05:09:21PM +020
On Thu, 26 Jul 2012, Vinod Koul wrote:
On Thu, 2012-07-26 at 15:58 +0900, Paul Mundt wrote:
On Thu, Jul 26, 2012 at 12:19:21PM +0530, Vinod Koul wrote:
On Wed, 2012-07-25 at 12:59 +0900, Paul Mundt wrote:
On Wed, May 09, 2012 at 05:09:21PM +0200, Guennadi Liakhovetski wrote
Hi Vinod
On Wed, 18 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 14:47 +0200, Guennadi Liakhovetski wrote:
> > > > Yes, that's right - these values have to be written to DMAC channel
> > > > configuration registers, so, we do not have to change anything, those
Hi Vinod
On Wed, 18 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 14:47 +0200, Guennadi Liakhovetski wrote:
Yes, that's right - these values have to be written to DMAC channel
configuration registers, so, we do not have to change anything, those
values can remain DMAC
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 12:55 +0200, Guennadi Liakhovetski wrote:
> > On Mon, 16 Jul 2012, Vinod Koul wrote:
> >
> > > On Mon, 2012-07-16 at 12:01 +0200, Guennadi Liakhovetski wrote:
> > > > On Mon, 16 Jul 2012, Vinod K
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 12:01 +0200, Guennadi Liakhovetski wrote:
> > On Mon, 16 Jul 2012, Vinod Koul wrote:
> >
> > > On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
> > > > > I want to know what
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
> > > I want to know what does ccr and mid_rid mean to dmac here?
> >
> > CHCR contains a few fields, some enable various interrupt sources, some
> > specify r
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 09:13 +0200, Guennadi Liakhovetski wrote:
> > > > They tell the driver how the channel has to be configured to
> > support this
> > > > specific client. They are values of two specific registers.
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 08:37 +0200, Guennadi Liakhovetski wrote:
> > On Mon, 16 Jul 2012, Vinod Koul wrote:
> >
> > > On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> > > > diff --git a/include/lin
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> > diff --git a/include/linux/sh_dma.h b/include/linux/sh_dma.h
> > index a79f10a..4e83f3e 100644
> > --- a/include/linux/sh_dma.h
> > +++ b/include/linux/sh
Hi Vinod
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> > This patch extends the sh dmaengine driver to support the preferred channel
> > selection and configuration method, instead of using the "private" field
Hi Vinod
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
This patch extends the sh dmaengine driver to support the preferred channel
selection and configuration method, instead of using the private field
from struct dma_chan. We add
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
diff --git a/include/linux/sh_dma.h b/include/linux/sh_dma.h
index a79f10a..4e83f3e 100644
--- a/include/linux/sh_dma.h
+++ b/include/linux/sh_dma.h
@@ -27,10 +27,10 @@ struct
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 08:37 +0200, Guennadi Liakhovetski wrote:
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
diff --git a/include/linux/sh_dma.h b/include/linux/sh_dma.h
index a79f10a
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 09:13 +0200, Guennadi Liakhovetski wrote:
They tell the driver how the channel has to be configured to
support this
specific client. They are values of two specific registers. In
fact, CHCR
means exactly
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
I want to know what does ccr and mid_rid mean to dmac here?
CHCR contains a few fields, some enable various interrupt sources, some
specify repeat- and renew-modes, others yet
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 12:01 +0200, Guennadi Liakhovetski wrote:
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
I want to know what does ccr and mid_rid mean to dmac here?
CHCR
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 12:55 +0200, Guennadi Liakhovetski wrote:
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 12:01 +0200, Guennadi Liakhovetski wrote:
On Mon, 16 Jul 2012, Vinod Koul wrote:
On Mon, 2012-07-16 at 10:47
Hi Paul, Magnus
On Thu, 12 Jul 2012, Paul Mundt wrote:
> On Thu, Jul 12, 2012 at 06:55:32AM +0900, Magnus Damm wrote:
> > Hi Guennadi,
> >
> > [CC Paul]
> >
> > On Thu, Jul 5, 2012 at 1:17 AM, Guennadi Liakhovetski
> > wrote:
> > > This
Hi Paul, Magnus
On Thu, 12 Jul 2012, Paul Mundt wrote:
On Thu, Jul 12, 2012 at 06:55:32AM +0900, Magnus Damm wrote:
Hi Guennadi,
[CC Paul]
On Thu, Jul 5, 2012 at 1:17 AM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
This patch extends the sh dmaengine driver to support
On Tue, 10 Jul 2012, Chris Ball wrote:
> Hi Guennadi,
>
> On Tue, Jul 10 2012, Guennadi Liakhovetski wrote:
> >> > The latter one looks big because of a rename, but with "-M" it's pretty
> >> > trivial. Chris, do you agree?
> >>
Hi Chris
On Tue, 10 Jul 2012, Chris Ball wrote:
> Hi Guennadi,
>
> On Wed, Jul 04 2012, Guennadi Liakhovetski wrote:
> > On Tue, 3 Jul 2012, Rafael J. Wysocki wrote:
> >
> >> On Tuesday, July 03, 2012, Guennadi Liakhovetski wrote:
> >> > Hi Rafael
&
Hi Chris
On Tue, 10 Jul 2012, Chris Ball wrote:
Hi Guennadi,
On Wed, Jul 04 2012, Guennadi Liakhovetski wrote:
On Tue, 3 Jul 2012, Rafael J. Wysocki wrote:
On Tuesday, July 03, 2012, Guennadi Liakhovetski wrote:
Hi Rafael
On Tue, 3 Jul 2012, Rafael J. Wysocki wrote
On Tue, 10 Jul 2012, Chris Ball wrote:
Hi Guennadi,
On Tue, Jul 10 2012, Guennadi Liakhovetski wrote:
The latter one looks big because of a rename, but with -M it's pretty
trivial. Chris, do you agree?
Is the minimal fix to just add | IRQF_ONESHOT to the request_threaded_irq
happen end of this / beginning of the next week.
Thanks
Guennadi
---
Guennadi Liakhovetski
--
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
Ple
On Mon, 25 Feb 2008, Greg KH wrote:
> On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote:
> > On Mon, 25 Feb 2008, Greg KH wrote:
> >
> > > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote:
> > > > On Mon, 25 F
On Mon, 25 Feb 2008, Greg KH wrote:
> On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote:
> > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
> >
> > > On Tue, 19 Feb 2008, Greg KH wrote:
> > >
> > > > On Mon, Feb 18, 2008 at
On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
> On Tue, 19 Feb 2008, Greg KH wrote:
>
> > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
> > > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
> > > getting the
On Tue, 19 Feb 2008, Greg KH wrote:
> On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
> > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
> > getting the following warnings (with a bit of context):
>
> Can you try enabling
On Tue, 19 Feb 2008, Greg KH wrote:
On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
getting the following warnings (with a bit of context):
Can you try enabling CONFIG_DEBUG_KOBJECT and sending
On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
On Tue, 19 Feb 2008, Greg KH wrote:
On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
getting the following warnings (with a bit of context
On Mon, 25 Feb 2008, Greg KH wrote:
On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote:
On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
On Tue, 19 Feb 2008, Greg KH wrote:
On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
Booting
On Mon, 25 Feb 2008, Greg KH wrote:
On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote:
On Mon, 25 Feb 2008, Greg KH wrote:
On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote:
On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
On Tue, 19
end of this / beginning of the next week.
Thanks
Guennadi
---
Guennadi Liakhovetski
--
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
MB PIIX4 USB (rev 01)
00:14.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
01:00.0 VGA compatible controller: Texas Instruments TVP4020 [Permedia 2] (rev
11)
Please say if .config is needed, although, theres nothing extraordinary
there wrt PCI / ACPI. Booting with "acpi=no
configuration.
Thanks
Guennadi
---
Guennadi Liakhovetski
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
configuration.
Thanks
Guennadi
---
Guennadi Liakhovetski
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
, theres nothing extraordinary
there wrt PCI / ACPI. Booting with acpi=noirq.
Thanks
Guennadi
---
Guennadi Liakhovetski
--
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
ue with timing ?
>
> I don't have HW access to this machine. If somebody could send one to me
> I could do more investigation.
Ben, would an ssh access to such a machine and to a terminal server
suffice?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the
and to a terminal server
suffice?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
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
On Thu, 14 Feb 2008, Guennadi Liakhovetski wrote:
> 2.6.24.2 fails to boot on the above system with an Intel DQ35JO
> motherboard, as do Debian install kernels - both stock etch amd64 and
> updated image from Kenshi Muto (kmuto.jp). The only way to boot was with
> "acpi=off
problems. Below is ubuntu's dmesg with a place marked where Debian and
self-compiled vanilla 2.6.24.2 kernels hang. Tried "pci=noacpi",
"acpi=noirq", "noapic", "nolapic", "pci=routeirq" with no success.
Thanks
Guennadi
---
Guennadi Liakhovet
. Below is ubuntu's dmesg with a place marked where Debian and
self-compiled vanilla 2.6.24.2 kernels hang. Tried pci=noacpi,
acpi=noirq, noapic, nolapic, pci=routeirq with no success.
Thanks
Guennadi
---
Guennadi Liakhovetski
[0.00] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc
On Thu, 14 Feb 2008, Guennadi Liakhovetski wrote:
2.6.24.2 fails to boot on the above system with an Intel DQ35JO
motherboard, as do Debian install kernels - both stock etch amd64 and
updated image from Kenshi Muto (kmuto.jp). The only way to boot was with
acpi=off. Whereas ubuntu 7.10
Introduce a is_valid_gpio() predicate to be used in gpiolib core and
drivers.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index d8db2f8..5390f46 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpi
David, you convinced me:-) I'll redo the patch. Just one comment:
On Sat, 9 Feb 2008, David Brownell wrote:
> On Saturday 09 February 2008, Guennadi Liakhovetski wrote:
>
> > And when those platforms share drivers, problems
> > arise. And the simple and efficient NO_IRQ noti
David, you convinced me:-) I'll redo the patch. Just one comment:
On Sat, 9 Feb 2008, David Brownell wrote:
On Saturday 09 February 2008, Guennadi Liakhovetski wrote:
And when those platforms share drivers, problems
arise. And the simple and efficient NO_IRQ notion, that would fis those
Introduce a is_valid_gpio() predicate to be used in gpiolib core and
drivers.
Signed-off-by: Guennadi Liakhovetski [EMAIL PROTECTED]
---
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index d8db2f8..5390f46 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -96,7
On Fri, 8 Feb 2008, David Brownell wrote:
> On Thursday 31 January 2008, Guennadi Liakhovetski wrote:
> > As discussed on i2c mailing list with David Brownell, and number
> > outside of the 0...MAX_INT range is invalid as a GPIO number.
> > Define a macro, similar
t; Right. In fact, every time you'd expect driver removal errors to
> cause module removal to fail. Maybe this is part of that whole
> "should we even *support* rmmod" discussion, which I tuned out.
We don't want to start another one here, do we?:-)
Thanks
Guennadi
---
Guenna
should we even *support* rmmod discussion, which I tuned out.
We don't want to start another one here, do we?:-)
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Fri, 8 Feb 2008, David Brownell wrote:
On Thursday 31 January 2008, Guennadi Liakhovetski wrote:
As discussed on i2c mailing list with David Brownell, and number
outside of the 0...MAX_INT range is invalid as a GPIO number.
Define a macro, similar to NO_IRQ, to be used as a deliberate
On Fri, 8 Feb 2008, David Brownell wrote:
> On Friday 08 February 2008, Guennadi Liakhovetski wrote:
> > As long as one or more GPIOs on a gpio chip are used its driver should not
> > be unloaded.
>
> The mechanism currently in place is to have gpiochip_remove() fai
it must be in obj-y.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
diff --git a/lib/Makefile b/lib/Makefile
index 543f250..7475da4 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -6,7 +6,7 @@ lib-y := ctype.o string.o vsprintf.o cmdline.o \
rbtree.o radix-tree.o dump_s
This uses the newly introduced owner field in struct gpio_chip to protect
pca953x from being unloaded as long as its GPIOs are in use.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
diff --git a/drivers/gpio/pca953x.c b/drivers/gpio/pca953x.c
index 0bd594d..89cee66
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
Note, that existing drivers do not have to be modified, for example those,
that are always statically linked in the kernel, a
On Fri, 8 Feb 2008, David Brownell wrote:
On Friday 08 February 2008, Guennadi Liakhovetski wrote:
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
The mechanism currently in place is to have gpiochip_remove() fail
if the platform's teardown
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
Signed-off-by: Guennadi Liakhovetski [EMAIL PROTECTED]
---
Note, that existing drivers do not have to be modified, for example those,
that are always statically linked in the kernel, as long
This uses the newly introduced owner field in struct gpio_chip to protect
pca953x from being unloaded as long as its GPIOs are in use.
Signed-off-by: Guennadi Liakhovetski [EMAIL PROTECTED]
---
diff --git a/drivers/gpio/pca953x.c b/drivers/gpio/pca953x.c
index 0bd594d..89cee66 100644
it must be in obj-y.
Signed-off-by: Guennadi Liakhovetski [EMAIL PROTECTED]
---
diff --git a/lib/Makefile b/lib/Makefile
index 543f250..7475da4 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -6,7 +6,7 @@ lib-y := ctype.o string.o vsprintf.o cmdline.o \
rbtree.o radix-tree.o dump_stack.o
On Thu, 31 Jan 2008, Guennadi Liakhovetski wrote:
> As discussed on i2c mailing list with David Brownell, and number
> outside of the 0...MAX_INT range is invalid as a GPIO number.
> Define a macro, similar to NO_IRQ, to be used as a deliberate
> invalid GPIO, rather than defining a i
On Thu, 31 Jan 2008, Guennadi Liakhovetski wrote:
As discussed on i2c mailing list with David Brownell, and number
outside of the 0...MAX_INT range is invalid as a GPIO number.
Define a macro, similar to NO_IRQ, to be used as a deliberate
invalid GPIO, rather than defining a is_valid_gpio
. The system is a dual [EMAIL PROTECTED], Compaq AP400. It is known to
have various ACPI bugs, so, this is just another one of them. No idea
whether or not this shall and can be fixed. At least wanted to document it
in case someone has a similar problem.
Thanks
Guennadi
---
Guennadi Liakhovetski
. The system is a dual [EMAIL PROTECTED], Compaq AP400. It is known to
have various ACPI bugs, so, this is just another one of them. No idea
whether or not this shall and can be fixed. At least wanted to document it
in case someone has a similar problem.
Thanks
Guennadi
---
Guennadi Liakhovetski
As discussed on i2c mailing list with David Brownell, and number
outside of the 0...MAX_INT range is invalid as a GPIO number.
Define a macro, similar to NO_IRQ, to be used as a deliberate
invalid GPIO, rather than defining a is_valid_gpio() macro.
Signed-off-by: Guennadi Liakhovetski <[EM
As discussed on i2c mailing list with David Brownell, and number
outside of the 0...MAX_INT range is invalid as a GPIO number.
Define a macro, similar to NO_IRQ, to be used as a deliberate
invalid GPIO, rather than defining a is_valid_gpio() macro.
Signed-off-by: Guennadi Liakhovetski [EMAIL
On Fri, 25 Jan 2008, Cyrill Gorcunov wrote:
> This patch does fix potential NULL pointer dereference
> due to logical typo error.
>
> The issue is pointed out by
> Guennadi Liakhovetski <[EMAIL PROTECTED]>
>
> Signed-off-by: Cyrill Gorcunov <[EMAIL PROTECTED]>
On Fri, 25 Jan 2008, Cyrill Gorcunov wrote:
This patch does fix potential NULL pointer dereference
due to logical typo error.
The issue is pointed out by
Guennadi Liakhovetski [EMAIL PROTECTED]
Signed-off-by: Cyrill Gorcunov [EMAIL PROTECTED]
---
Index: linux-2.6.git/drivers/media
review this file and the whole
commit it came in with properly...
Thanks
Guennadi
---
Guennadi Liakhovetski
--
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-in
we want to document it somewhere? Wasn't C-sources originally
supposed to be ASCII? So, what we use in sources, what under Documentation
or in MAINTAINERS may be different matters?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line "unsubscribe l
it somewhere? Wasn't C-sources originally
supposed to be ASCII? So, what we use in sources, what under Documentation
or in MAINTAINERS may be different matters?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
need to manually enable something or run some user-space
> app?!
> >
> > It depends - different options have it differently. Most simple ones
> are
> > just compile-time, so, you don't have to enable them. Look in "help"
> for
> > respective debug-options.
ally enable something or run some user-space app?!
It depends - different options have it differently. Most simple ones are
just compile-time, so, you don't have to enable them. Look in "help" for
respective debug-options.
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscrib
some user-space app?!
It depends - different options have it differently. Most simple ones are
just compile-time, so, you don't have to enable them. Look in help for
respective debug-options.
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line unsubscribe
don't have to enable them. Look in help
for
respective debug-options.
Thanks
Guennadi
---
Guennadi Liakhovetski
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
when something is wrong ;)
> >
>
>
> --
> 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.
something is wrong ;)
--
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/
---
Guennadi Liakhovetski
On Mon, 3 Dec 2007, Pavel Machek wrote:
> On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
> > On Sun, 2 Dec 2007, Pavel Machek wrote:
> >
> > > > I compiled a .24-ish kernel for it with CONFIG_NO_HZ and
> > > > CONFIG_HIGH_RES_TIMERS. To g
On Mon, 3 Dec 2007, Pavel Machek wrote:
On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
On Sun, 2 Dec 2007, Pavel Machek wrote:
I compiled a .24-ish kernel for it with CONFIG_NO_HZ and
CONFIG_HIGH_RES_TIMERS. To get the system boot at least sometimes I
have
On Tue, 4 Dec 2007, Robert Hancock wrote:
> Guennadi Liakhovetski wrote:
> >
> > I've got an old 2xP-II @ 400MHz Compaq AP400 system, which I'm still using.
> > It has many peculiarities, so, I wouldn't be surprised if the answer to my
> > questions would be "s
On Tue, 4 Dec 2007, Robert Hancock wrote:
Guennadi Liakhovetski wrote:
I've got an old 2xP-II @ 400MHz Compaq AP400 system, which I'm still using.
It has many peculiarities, so, I wouldn't be surprised if the answer to my
questions would be sorry, the patient is rather dead than alive
On Mon, 3 Dec 2007, Pavel Machek wrote:
> On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
> > On Sun, 2 Dec 2007, Pavel Machek wrote:
>
> > > > CR0: 8005003b CR2: 081dcf88 CR3: 07e46000 CR4: 02d0
> > > > DR0: DR1: DR2:
DR1: DR2: DR3:
> > DR6: 0ff0 DR7: 0400
> > [] show_trace_log_lvl+0x1a/0x30
> > [] show_trace+0x12/0x20
>
> ...and disable softlockup watchdog, too...
So, you think those BUGs are bogus?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
] show_trace_log_lvl+0x1a/0x30
[c0105f42] show_trace+0x12/0x20
...and disable softlockup watchdog, too...
So, you think those BUGs are bogus?
Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
701 - 800 of 1041 matches
Mail list logo
