On Tue, 2008-09-02 at 15:12 +0200, David Jander wrote:
> I have made some astonishing discoveries, and I'd like to post the
> used source-code somewhere in the meantime, any suggestions? To this list?
Yes, mail it.
I got a mpc8323/8321 board I want to try.
> For the MPC5121e, 16-register strides
On Tue, Sep 2, 2008 at 8:01 PM, Arnd Bergmann <[EMAIL PROTECTED]> wrote:
> On Tuesday 02 September 2008, Li Yang wrote:
>> Some of Freescale SoC chips have a QE or CPM co-processor which
>> supports full speed USB. The driver adds device mode support
>> of both QE and CPM USB controller to Linux U
HAVE_ARCH_UNMAPPED_AREA and HAVE_ARCH_UNMAPPED_AREA_TOPDOWN must
be defined whenever CONFIG_PPC_MM_SLICES is enabled, not only when
CONFIG_HUGETLB_PAGE is. They used to be always defined together but
this is no longer the case.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
---
arch/p
On Wed, 2008-09-03 at 01:46 +0200, Christoph Hellwig wrote:
> On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> > > Yes. Merge your code or live with the pain of things changing
> > > underneath. Period.
> >
> > Pain isn't for me :-) It's for those writing userspace stuff b
On Tue, Sep 02, 2008 at 06:14:38PM -0600, Gary Thomas wrote:
> David Gibson wrote:
>> On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
>
>>> What gives? Why is explicit hex sometimes an error and sometimes not?
>>
>> Because we changed the format at one point. Originally (the "dts-
On Tue, Sep 02, 2008 at 12:12:27PM -0500, Jon Tollefson wrote:
> David Gibson wrote:
> > When BenH and I were looking at the new code for handling 16G pages,
> > we noticed a small bug. It doesn't actually break anything user
> > visible, but it's certainly not the way things are supposed to be.
>
David Gibson wrote:
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
What gives? Why is explicit hex sometimes an error and sometimes not?
Because we changed the format at one point. Originally (the "dts-v0"
format) it was implicitly hex everywhere, which turned out to be a
m
On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> > Yes. Merge your code or live with the pain of things changing
> > underneath. Period.
>
> Pain isn't for me :-) It's for those writing userspace stuff based on
> my kernel changing all the time :-)
They can wait until it'
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
> What gives? Why is explicit hex sometimes an error and sometimes not?
> Is the format of this file documented anywhere (I've not found it)?
If the file has /dts-v1/; at the top, it uses version 1 of the device
tree syntax, which has C
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
> Following on with my RTC problem, I cut&pasted this from
> the TQM5200 dts file:
> [EMAIL PROTECTED] {
> #address-cells = <1>;
> #size-cells = <0>;
>
On Tue, 2008-09-02 at 17:16 -0500, Jon Tollefson wrote:
> Benjamin Herrenschmidt wrote:
> >> Actually, Jon has been hitting an occasional pagetable lock related
> >> problem. The last theory was that it might be some sort of race but it's
> >> vaguely possible that this is the issue. Jon?
> >>
> Then don't try to reserve a system call to be used only by an out-of-tree,
> proprietary kernel extension. Which your kernel change in essence is
> until it's released.
>
> Would we accept a system call number reservation that was submitted by,
> say, nVidia? No? Well, there you go.
>
> It's r
Hi Konstantinos,
I've been on vacation. Here are my responses.
On Sun, 2008-08-24 at 11:03 +0300, Konstantinos Margaritis wrote:
> Copyright assignment is not the issue, if there was interest in the first
> place, that would never had deterred me.
Okay. This does deter some people when they u
Benjamin Herrenschmidt wrote:
>> Actually, Jon has been hitting an occasional pagetable lock related
>> problem. The last theory was that it might be some sort of race but it's
>> vaguely possible that this is the issue. Jon?
>>
>
> All hugetlbfs ops should be covered by the big PTL except wal
On Wed, Sep 03, 2008 at 07:49:10AM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2008-09-02 at 16:30 -0500, Olof Johansson wrote:
> > On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> > > On Tue, 2008-09-02 at 13:06 -0500, Olof Johansson wrote:
> > > > On Tue, Sep 02, 2008
Following on with my RTC problem, I cut&pasted this from
the TQM5200 dts file:
[EMAIL PROTECTED] {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,mpc5200-i2c","fsl-i2c";
reg
On Tue, 2008-09-02 at 16:30 -0500, Olof Johansson wrote:
> On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2008-09-02 at 13:06 -0500, Olof Johansson wrote:
> > > On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> > > > Some stuff I'm workin
Scott Wood wrote:
On Tue, Sep 02, 2008 at 03:28:19PM -0600, Gary Thomas wrote:
I'm working with a couple FreeScale platforms and having
trouble getting the RTC which is connected via I2C to work.
I had this working fine in the old arch/ppc tree, but it's
failing in the arch/powerpc world.
Make
On Tue, Sep 02, 2008 at 03:28:19PM -0600, Gary Thomas wrote:
> I'm working with a couple FreeScale platforms and having
> trouble getting the RTC which is connected via I2C to work.
> I had this working fine in the old arch/ppc tree, but it's
> failing in the arch/powerpc world.
Make sure the rtc
I'm working with a couple FreeScale platforms and having
trouble getting the RTC which is connected via I2C to work.
I had this working fine in the old arch/ppc tree, but it's
failing in the arch/powerpc world.
Here's the problem - the RTC driver gets initialized *before*
the I2C bus and as far a
> The reason I did that was to distinguish between the size of a
> software PTE entry, and the actual size of the hardware entry. In the
> case of 36b physical, the hardware PTE size is the same as it always
> is; but we've grown the Linux PTE. We can call it something else, or
> I can c
On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2008-09-02 at 13:06 -0500, Olof Johansson wrote:
> > On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> > > Some stuff I'm working on that isn't released yet needs
> > > a syscall number but I c
> Actually, Jon has been hitting an occasional pagetable lock related
> problem. The last theory was that it might be some sort of race but it's
> vaguely possible that this is the issue. Jon?
All hugetlbfs ops should be covered by the big PTL except walking... Can
we have more info about the pro
On Tue, 2008-09-02 at 13:06 -0500, Olof Johansson wrote:
> On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> > Some stuff I'm working on that isn't released yet needs
> > a syscall number but I can't say what it's for until I
> > get permission to release it :-)
> >
> > In
On Tue, 2008-09-02 at 08:08 -0400, Josh Boyer wrote:
> On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> >Some stuff I'm working on that isn't released yet needs
> >a syscall number but I can't say what it's for until I
> >get permission to release it :-)
> >
> >In the meant
On Mon, Sep 01, 2008 at 11:27:59AM +0100, Martyn Welch wrote:
> +static __initdata struct of_device_id of_bus_ids[] = {
> + { .compatible = "simple-bus", },
> + { .type = "serial", },
> + { .type = "soc", },
> + { .type = "i2c", },
i2c and serial don't belong here, and soc is redun
On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> Some stuff I'm working on that isn't released yet needs
> a syscall number but I can't say what it's for until I
> get permission to release it :-)
>
> In the meantime, it would be nice if a number could be set
> aside so th
David Gibson wrote:
> When BenH and I were looking at the new code for handling 16G pages,
> we noticed a small bug. It doesn't actually break anything user
> visible, but it's certainly not the way things are supposed to be.
> The 16G patches didn't update the huge_pte_offset() and
> huge_pte_all
On 02.09.2008 [13:44:42 +0100], Mel Gorman wrote:
> On (02/09/08 15:05), David Gibson didst pronounce:
> > When BenH and I were looking at the new code for handling 16G pages,
> > we noticed a small bug. It doesn't actually break anything user
> > visible, but it's certainly not the way things are
On Sep 1, 2008, at 12:19 AM, Benjamin Herrenschmidt wrote:
Thanks for taking the time to dig through this :)
+#ifdef CONFIG_PTE_64BIT
+#define PTE_FLAGS_OFFSET 4 /* offset of PTE flags, in bytes */
+#define LNX_PTE_SIZE 8 /* size of a linux PTE, in bytes */
+#else
On Monday 01 September 2008 11:36:15 Joakim Tjernlund wrote:
>[...]
> > Then I started my test program with LD_PRELOAD=...
> >
> > My test program only copies big chunks of aligned memory, so it will only
> > test for maximum throughput (such as copying video frames). I will make a
> > better one,
On (02/09/08 15:05), David Gibson didst pronounce:
> When BenH and I were looking at the new code for handling 16G pages,
> we noticed a small bug. It doesn't actually break anything user
> visible, but it's certainly not the way things are supposed to be.
> The 16G patches didn't update the huge_
On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
>Some stuff I'm working on that isn't released yet needs
>a syscall number but I can't say what it's for until I
>get permission to release it :-)
>
>In the meantime, it would be nice if a number could be set
>aside so the tool
On Tuesday 02 September 2008, Li Yang wrote:
> Some of Freescale SoC chips have a QE or CPM co-processor which
> supports full speed USB. The driver adds device mode support
> of both QE and CPM USB controller to Linux USB gadget. The
> driver is tested with MPC8360 and MPC8272, and should work w
ok. I will try the serial layer
2008/9/2, Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
>
> On Tue, 2008-09-02 at 09:34 +0200, Sébastien Chrétien wrote:
> > ok is it a bad way to write a tty driver ? why ?
>
>
> Not necessarily, it's just overkill. The UART layer handles a lot
> of stuff for you. Th
On Tue, 2008-09-02 at 09:34 +0200, Sébastien Chrétien wrote:
> ok is it a bad way to write a tty driver ? why ?
Not necessarily, it's just overkill. The UART layer handles a lot
of stuff for you. The tty layer is tricky to get right.
Cheers,
Ben.
___
L
On Tue, 2008-09-02 at 16:12 +0800, Li Yang-R58472 wrote:
> > -Original Message-
> > From: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, September 02, 2008 3:57 PM
> > To: Li Yang-R58472
> > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> > [EMAIL PROTECTED]; [EMAIL PROTECTED];
> -Original Message-
> From: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 02, 2008 3:57 PM
> To: Li Yang-R58472
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; linuxppc-dev@ozlabs.org
> Subject: Re: [PATCH]
On Tue, 2008-09-02 at 15:35 +0800, Li Yang wrote:
> On Tue, Sep 2, 2008 at 1:11 AM, Anton Vorontsov
> <[EMAIL PROTECTED]> wrote:
> > On Thu, Aug 28, 2008 at 05:43:33PM +0800, Li Yang wrote:
> >> Some of Freescale SoC chips have a QE or CPM co-processor which
> >> supports full speed USB. The drive
On Tue, Sep 2, 2008 at 1:11 AM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 05:43:33PM +0800, Li Yang wrote:
>> Some of Freescale SoC chips have a QE or CPM co-processor which
>> supports full speed USB. The driver adds device mode support
>> of both QE and CPM USB control
ok is it a bad way to write a tty driver ? why ?
2008/9/2, Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
>
> On Tue, 2008-09-02 at 07:13 +0200, Sébastien CHRETIEN wrote:
> > My board has only a uart device on a FPGA. I don't use the serial layer
> > because it isn't documented in Linux Device Driver
On Mon, Sep 1, 2008 at 9:52 PM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 05:43:33PM +0800, Li Yang wrote:
>> Some of Freescale SoC chips have a QE or CPM co-processor which
>> supports full speed USB. The driver adds device mode support
>> of both QE and CPM USB control
42 matches
Mail list logo
