On Thursday 25 June 2009, Steven A. Falco wrote:
> + if (spi->mode & ~MODEBITS) {
> + dev_dbg(&spi->dev, "setup: unsupported mode bits %x\n",
> + spi->mode & ~MODEBITS);
> + return -EINVAL;
> + }
This wasn't tested against 2.6.30-rc1 wa
On Thu, Jun 25, 2009 at 9:11 AM, Frank
Prepelica wrote:
> Hi all,
>
> we removed the ethernet PHYs (MARVELL) from our customized board (based on
> MPC8313ERDB) and
> connected the CPU Ethernet lines directly to a FPGA which is now emulating
> the PHY. But the ifconfig
> command cannot find that e
kernel mailz wrote:
So this means
when kernel gets interrupted by app which may be in PID=5 (say)
kernel translations for PID=0 remain valid ?
I am not able to follow Scott
Yes, exactly. They're valid even in userspace, except to the extent that the
kernel marks them supervisor-only.
-Scott
This adds a SPI driver for the SPI controller found in the IBM/AMCC
4xx PowerPC's.
Signed-off-by: Stefan Roese
Signed-off-by: Wolfgang Ocker
Acked-by: Josh Boyer
Signed-off-by: Steven A. Falco
---
Note, I have not removed any of the prior sign-offs, but feel free to
look this version over very
Stefan suggested that I try to address the comments against the PPC4xx
SPI driver, so here goes...
A post of version 7 of the driver will follow this email, but I thought
it might make it easier on everyone to inline my comments here. Hence,
this brief, introductory "top post".
> On Thursday 08
Hi,
I have a SMP linux running on 85xx poweprc. Say on Core 0 and Core 1
two different processes are running and on both the schedular runs.
Now for some special case, if one of my process issues a ioctl which
gets serviced by a kernel module, I wish to slow the schedular on that
core only. Otherw
On Jun 25, 2009, at 12:52 PM, kernel mailz wrote:
If an aap has to be placed in AS=1 and it issues an ioctl, kernel
needs to be modified ?
Correct, this would be a significant change to the kernel.
I guess the PID=0 trick will work when AS is same
right ?
correct.
- k
On 6/25/09, Kum
If an aap has to be placed in AS=1 and it issues an ioctl, kernel
needs to be modified ?
I guess the PID=0 trick will work when AS is same
right ?
On 6/25/09, Kumar Gala wrote:
> That is correct. The PID = 0 translations are always valid.
>
> - k
>
> On Jun 25, 2009, at 5:51 AM, kernel mailz
That is correct. The PID = 0 translations are always valid.
- k
On Jun 25, 2009, at 5:51 AM, kernel mailz wrote:
So this means
when kernel gets interrupted by app which may be in PID=5 (say)
kernel translations for PID=0 remain valid ?
I am not able to follow Scott
-TZ
On Thu, Jun 25, 2009
Adrian Reber wrote on 11.06.2009 12:52:17:
>
> I forgot about this patch. Can this still be merged?
>
>
> On Thu, Mar 26, 2009 at 01:05:42PM +0100, Adrian Reber wrote:
> > Using the RTAS watchdog driver to read out the temperature crashes
> > on a PXCAB:
> >
> > Unable to handle kernel paging r
So this means
when kernel gets interrupted by app which may be in PID=5 (say)
kernel translations for PID=0 remain valid ?
I am not able to follow Scott
-TZ
On Thu, Jun 25, 2009 at 4:22 AM, Scott Wood wrote:
> kernel mailz wrote:
>>
>> But If the app was running with PID=1, interrupt occurs, kern
Hi all,
we removed the ethernet PHYs (MARVELL) from our customized board (based on
MPC8313ERDB) and
connected the CPU Ethernet lines directly to a FPGA which is now emulating the
PHY. But the ifconfig
command cannot find that eth device anymore. Does the emulated PHY needs to
provide MDIO
in
On Wed, 2009-06-24 at 23:16 +0530, kernel mailz wrote:
> But If the app was running with PID=1, interrupt occurs, kernel code
> gets executed in PID=1, how does the kernel handle this ? and goes
> back to PID=0, since its translations are all in PID=0
PID 0 is a special case in HW. TLB entries wit
> > 1. User code executes ioctl
> > 2. interrupt goes to the kernel
>
> On the interrupt the PR changes from 0 -> 1
The other way around actually :-)
> > 3. ioctl handler in driver gets invoked
> > The buffer pointer still contains 0x1.
> >
> > How kernel code running in PR=0 accesses it an
On Thu, 2009-06-25 at 13:22 +0200, Utz Bacher wrote:
>
> Adrian Reber wrote on 11.06.2009 12:52:17:
> >
> > I forgot about this patch. Can this still be merged?
Probably, can you re-send it in proper format to the list so it gets
into patchwork (unless it's already there in which case I'll pick
On Thu, Jun 25, 2009 at 11:02:36AM +0400, Anton Vorontsov wrote:
[...]
> Of course, it could be that the root cause of the problems
> I observe is weird NIC on my host. Well, then QA team should
> have used the same broken NIC on their hosts. :-)
>
> I can easily test it by interconnecting two tar
From: Anton Vorontsov
Date: Thu, 25 Jun 2009 11:08:13 +0400
> On Thu, Jun 25, 2009 at 05:02:32AM +0400, Anton Vorontsov wrote:
>> Currently the half-duplex operation seems to not work reliably for
>> RGMII PHY interfaces. It takes about 10 minutes to boot NFS rootfs
>> using 10/half link, followi
On Thu, Jun 25, 2009 at 05:02:32AM +0400, Anton Vorontsov wrote:
> Currently the half-duplex operation seems to not work reliably for
> RGMII PHY interfaces. It takes about 10 minutes to boot NFS rootfs
> using 10/half link, following symptoms were observed:
David, please ignore these patches, the
On Wed, Jun 24, 2009 at 10:11:14PM -0700, Mark Huth wrote:
> Anton Vorontsov wrote:
>> Currently the half-duplex operation seems to not work reliably for
>> RGMII/GMII PHY interfaces. It takes about 10 minutes to boot NFS
>> rootfs using 10/half link, following symptoms were observed:
>>
>> ucc_g
19 matches
Mail list logo
