usionHDTV5 Gold
Flags: bus master, medium devsel, latency 64, IRQ 19
Memory at fd00 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
--
Scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
On Oct 4, 2007, at 11:52 AM, Scott wrote:
I'm having what I think is a PCI bus problem.
I have a ASUS P5B Intel 965 motherboard and a DVICO Fusion HDTV5 RT
adapter on the PCI bus. When this adapter is recording (anything) I
see
pci_abort messages repeating in the /var/log/messages fil
On Sat, 2007-10-06 at 12:48 -0600, Robert Hancock wrote:
> > On Oct 4, 2007, at 11:52 AM, Scott wrote:
> >
> >> I'm having what I think is a PCI bus problem.
> >>
> >> I have a ASUS P5B Intel 965 motherboard and a DVICO Fusion HDTV5 RT
> >> a
On Oct 8, 2007, at 3:44 AM, Gerd Hoffmann wrote:
Scott wrote:
On Sat, 2007-10-06 at 12:48 -0600, Robert Hancock wrote:
Oct 2 21:59:32 htpc cx88[0]: irq mpeg [0x8] pci_abort*
Oct 2 21:59:32 htpc cx88[0]/2-mpeg: general errors: 0x0008000
I assumed it was an interrupt issue based on
alhost:/opt/nfs/ /mnt/tmp
mars:~# echo "Hello" > /mnt/tmp/test-file
mars:~# echo "Hello" > /mnt/tmp/test-file
bash: /mnt/tmp/test-file: Invalid argument
Can you show an strace of this please? Also, might suggest "rpcdebug -
m nfsd -s all"
--
Scott
--
To uns
ware. Either memory or the mobo/riser
card the memory is on. You might try lowering the memory timings of your
memory in BIOS. Try removing 1/2 of your memory. If it still remove the
other 1/2 and put the first 1/2 back and try again.
--
Scott <[EMAIL PROTECTED]>
--
To unsubscribe from this l
deliver testing for you, so that you get to know
our quality first hand.
If you want to explore further, please reply back.
Thanks and Regards,
Scott
deliver testing for you, so that you get to know
our quality first hand.
If you want to explore further, please reply back.
Thanks and Regards,
Scott
From: Scott Liu
This patch is for Elan eKTH Touchscreen product, I2C adpater module.
Signed-off-by: Scott Liu
---
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile |1 +
drivers/input/touchscreen/elants_i2c.c | 1789
3
relies on "struct vcpu" in kvm_host.h.
Why can't the entirety kvm_host.h be included regardless of CONFIG_KVM,
just like most other feature-specific headers? Why can't the if/else
just go around the functions that you want to stub out for non-KVM
builds?
-Scott
--
To u
ivate-data of the IOMMU domain. Instead
I
added a DOMAIN_ATTR_WINDOWS attribute to get/set the number of
subwindows. I'll post the updated patch-set soon.
If it's private data, how does the caller know what sort of geometry it
can request?
-Scott
--
To unsubscribe from this list:
labs.org/patch/211454/
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
no idea that a violation has occurred. It's going to keep on
writing to bad data.
I think that's only the case for posted writes (or devices which fail
to take a hint and stop even after they see an I/O error).
-Scott
--
To unsubscribe from this list: send the line "unsubscribe
se it any way they like with
attribution) than the GPLv3-style (use it our way, or else).
But then, EXPORT_SYMBOL_GPL didn't exist then. And I think its existence
is silliness on the part of several hard-core developers.
scott lurndal
--
To unsubscribe from this list: send the line "unsu
On Feb 12, 2008 1:17 AM, Scott Lovenberg <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> On Feb 12, 2008 12:23 AM, Peter Teoh <[EMAIL PROTECTED]> wrote:
>
> >
> > I was looking for documentation on the kstack_depth_to_print under
> > /proc/sys/kerne
Randy Dunlap wrote:
On Wed, 13 Feb 2008 09:08:12 +0700 Mulyadi Santosa wrote:
Hi all...
Here's my idea: what if we collaborate to extend and make the kernel
documentation better? I have done (slow) start by editing profile=
kernel param. It's not accepted by Adrian Bunk, but at least I di
On Thu, 14 Feb 2008, Greg Kroah-Hartman wrote:
> This removes the depandancy of the cpcihp driver from the PCI_LEGACY
> config option by removing its usage of the pci_find_bus() function.
>
>
> Cc: Kristen Carlson Accardi <[EMAIL PROTECTED]>
> Cc: Scott Murray <[EMAIL
fic stash id parameter through IOMMU API.
> 3. Added an attribute for enabling/disabling DMA to a particular
>memory window.
>
>
> Signed-off-by: Varun Sethi
> ---
> changes in v4:
> - Updated comment explaining subwindows(as mentioned by Scott).
> change in v3:
seudo-bitfield. "7 == reserved" doesn't make much
sense -- that would leave a lot of other values neither defined nor
explicitly reserved.
That said, the "See PAACE_DA_*" comment should be sufficient and avoids
making people have to care about what bitfield ordering t
ort"
>>
>> * no change to the rest of the patch set
>
> Hi Kumar,
>
> How about picking about this series for 3.6? The review seems to
> settle down for this revision.
>
>
> Hi Scott,
>
> Thanks for the review comments provided. We'd like to get
This patch is for Elan eKTF Touchscreen product, I2C adpater module.
Signed-off-by: Scott Liu
---
Hi Dmitry,
v3 chagnes:
* remove elants_prove() thread.
* follow standard kernel-doc.
* sysfs only for device information
have it claim that device (preferably with an atomic unbind from the
previous driver). We shouldn't be messing around with compatible
(either modifying it or telling VFIO which compatibles to look for) when
we know the specific devices (not just type of devices) we want to bind.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 2013-10-01 at 14:15 -0500, Scott Wood wrote:
> On Tue, 2013-10-01 at 13:38 -0500, Kim Phillips wrote:
> > Hi,
> >
> > Santosh and I are having a problem figuring out how to enable binding
> > (and re-binding) platform devices to a platform VFIO driver (see
&
On Tue, 2013-10-01 at 16:59 -0500, Kim Phillips wrote:
> On Tue, 1 Oct 2013 14:15:38 -0500
> Scott Wood wrote:
>
> > I think the ideal interface would be if you could write the sysfs device
> > name into the vfio bind file (or some new file in the same directory),
>
nuxfoundation.org; linux-
> > ker...@vger.kernel.org; a.mota...@virtualopensystems.com; ag...@suse.de;
> > Yoder Stuart-B08248; Wood Scott-B07421; Sethi Varun-B16395; Bhushan
> > Bharat-R65777; peter.mayd...@linaro.org; santosh.shu...@linaro.org;
> > k...@vger.kernel.org
> &g
On Wed, 2013-10-02 at 11:43 -0700, Christoffer Dall wrote:
> On Wed, Oct 02, 2013 at 01:32:38PM -0500, Scott Wood wrote:
> > On Wed, 2013-10-02 at 13:25 -0500, Yoder Stuart-B08248 wrote:
> > >
> > > > -Original Message-
> > > > From: Christoffe
On Wed, 2013-10-02 at 21:13 +0100, Christoffer Dall wrote:
> On Wed, Oct 02, 2013 at 03:04:15PM -0500, Kim Phillips wrote:
> > On Wed, 2 Oct 2013 11:43:30 -0700
> > Christoffer Dall wrote:
> >
> > > On Wed, Oct 02, 2013 at 01:32:38PM -0500, Scott Wood wrote:
> &
bind won't work if it driver_match_device() fails. PCI has
PCI_ANY_ID, so the missing piece for PCI is a way to say that the driver
should not bind to a device except when explicitly requested via sysfs
bind.
I don't see any equivalent functionality to PCI_ANY_ID for platform
devices.
-Sco
On Wed, 2013-10-02 at 14:16 -0700, gre...@linuxfoundation.org wrote:
> On Wed, Oct 02, 2013 at 04:08:41PM -0500, Scott Wood wrote:
> > On Wed, 2013-10-02 at 13:37 -0700, gre...@linuxfoundation.org wrote:
> > > On Wed, Oct 02, 2013 at 11:43:30AM -0700, Christoffer Dall wrote:
>
On Wed, 2013-10-02 at 16:40 -0700, gre...@linuxfoundation.org wrote:
> On Wed, Oct 02, 2013 at 04:35:15PM -0500, Scott Wood wrote:
> > On Wed, 2013-10-02 at 14:16 -0700, gre...@linuxfoundation.org wrote:
> > > On Wed, Oct 02, 2013 at 04:08:41PM -0500, Scott Wood wrote:
>
On Thu, 2013-10-03 at 11:54 -0700, gre...@linuxfoundation.org wrote:
> On Thu, Oct 03, 2013 at 01:33:27PM -0500, Scott Wood wrote:
> > What it looks like we do still want from the driver core is the ability
> > for a driver to say that it should not be bound to a device except v
r: Device Busy
Is the caam_jr driver printing this, or the device model infrastructure?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.
/boot/dts/fsl/elo3-dma-1.dtsi
Please update Documentation/devicetree/bindings/powerpc/fsl/dma.txt for
the new compatible and dgsr1.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordo
On Fri, 2013-09-13 at 07:04 +0200, leroy christophe wrote:
> Le 12/09/2013 20:44, Scott Wood a écrit :
> > On Thu, 2013-09-12 at 20:25 +0200, Christophe Leroy wrote:
> >> This is a reorganisation of the setup of the TLB at kernel startup, in
> >> order
> >>
en because
> all 8 channels must always be present in the Elo3 IP block.
If a channel is not usable for whatever reason (other than that "used
for a different fixed purpose and thus described with a different
compatible" thing that was mentioned earlier in these threads), wouldn't
i
mpc8349, mpc8360, etc.) and the second is
> > >> - "fsl,elo-dma"
> > >> -- reg :
> > >> -- ranges: Should be defined as specified in 1) to
> > >> describe the
> > >> -
> buffer enough to hold all things.
>
> It is also necessary to be sure of 'ses->domainName' must be less than
> 256, and define the related macro instead of hard code number '256'.
>
> Signed-off-by: Chen Gang
> Reviewed-by: Jeff Layton
> Reviewed-b
7;t see any setting of SPRN_MD_CTR after this code,
so won't it overwrite entry 30 (the middle 8M) in the CONFIG_PIN_TLB
case?
Ben, would patches like this be considered bugfixes as far as merging
goes, or would they be for next given that it's something that's never
really worked
mtspr SPRN_MI_AP, r8
> mtspr SPRN_MD_AP, r8
>
> + /* Always pin the first 8 MB ITLB to prevent ITLB
> + * misses while mucking around with SRR0/SRR1 in asm
> + */
> + lis r8, (MI_RSV4I | MI_RESETVAL)@h
> + mtspr SPRN_MI_CTR, r8 /*
difference is that (if I understand correctly) PCs handle MSIs
specially, via interrupt remapping, rather than being translated as a
normal memory access through the IOMMU.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is assigned a index number.
> + * index number ranges from 0 to 2^32.
> + * Example MSI bank 1 = 0
> + * MSI bank 2 = 1, and so on.
> + */
> + int bank_index;
2^32 doesn't fit in "int" (nor does 2^32 - 1).
Just say that indices start at 0.
So I think the value we keep here should be a phys_addr_t (it
comes straight from the MMIO address in the device tree), which gets
trivially turned into a dma_addr_t by the non-VFIO code path because
there's currently no translation there.
-Scott
--
To unsubscribe from this list: send
On Wed, 2013-10-09 at 14:02 -0500, Yoder Stuart-B08248 wrote:
> Have been thinking about this issue some more. As Scott mentioned,
> 'wildcard' matching for a driver can be fairly done in the platform
> bus driver. We could add a new flag to the platform driver struct:
>
On Wed, 2013-10-09 at 12:16 -0700, gre...@linuxfoundation.org wrote:
> On Wed, Oct 09, 2013 at 07:02:25PM +, Yoder Stuart-B08248 wrote:
> > Have been thinking about this issue some more. As Scott mentioned,
> > 'wildcard' matching for a driver can be fairly done in th
On Wed, 2013-10-09 at 14:44 -0500, Yoder Stuart-B08248 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Wednesday, October 09, 2013 2:22 PM
> > To: Yoder Stuart-B08248
> > Cc: Wood Scott-B07421; Kim Phillips; Christoffer Dall;
On Thu, 2013-10-10 at 02:45 -0500, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Thursday, October 10, 2013 1:33 AM
> > To: Yoder Stuart-B08248
> > Cc: Wood Scott-B07421; Kim Phillips; Christoffer Dall; Ale
On Thu, 2013-10-10 at 03:01 -0500, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> > Behalf Of
> > Kim Phillips
> > Sent: Thursday, October 10, 2013 8:36 AM
> > To:
t node's ranges are set up (sometimes we
want to be that specific, but usually not).
> to say "how many entries", to say "register functions and even names"?
If there's more than one
entry/resource/whatever-we-decide-to-call-it-but-let's-pick-somethin
org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> > linux-
> > ker...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> > p...@vger.kernel.org; ag...@suse.de; Wood Scott-B07421; iommu@lists.linux-
> > foundation.org; Bhushan Bharat-R65777
> > Subject: Re:
emented to a value within the first 28 entries
(MD_RSV4D is set)...".
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 2013-09-17 at 18:40 +0200, leroy christophe wrote:
> Le 16/09/2013 23:02, Scott Wood a écrit :
> > On Fri, 2013-09-13 at 07:04 +0200, leroy christophe wrote:
> >> Le 12/09/2013 20:44, Scott Wood a écrit :
> >>> On Thu, 2013-09-12 at 20:25 +0200, Christophe
duce normal output? If not, I guess you
could make a tool that creates a wrapper file that includes the main
file and then evaluates the symbol you want.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kern
On 10/10/2012 10:15:17 AM, Stephen Warren wrote:
On 10/09/2012 06:04 PM, Scott Wood wrote:
> On 10/09/2012 06:20:53 PM, Mitch Bradley wrote:
>> On 10/9/2012 11:16 AM, Stephen Warren wrote:
>> > On 10/01/2012 12:39 PM, Jon Loeliger wrote:
>> >>>
>> >>
395
> Cc: linux-kernel@vger.kernel.org; io...@lists.linux-foundation.org;
Wood
> Scott-B07421; linuxppc-...@lists.ozlabs.org; Tabi Timur-B04825
> Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes
> required by fsl PAMU driver.
>
> Hmm, we need to work out a good abst
Of Joerg Roedel
> > Sent: Sunday, December 02, 2012 7:33 PM
> > To: Sethi Varun-B16395
> > Cc: linux-kernel@vger.kernel.org;
io...@lists.linux-foundation.org; Wood
> > Scott-B07421; linuxppc-...@lists.ozlabs.org; Tabi Timur-B04825
> > Subject: Re: [PATCH 3/4 v5] iommu/fsl
On 12/04/2012 05:53:33 AM, Sethi Varun-B16395 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, December 03, 2012 10:34 PM
> To: Sethi Varun-B16395
> Cc: Joerg Roedel; linux-kernel@vger.kernel.org; iommu@lists.linux-
> foundation.org; Wood Scot
{
DOMAIN_ATTR_MAX,
DOMAIN_ATTR_GEOMETRY,
+ /* Set the IOMMU hardware stashing
+* parameters.
+*/
+ DOMAIN_ATTR_STASH,
+ /* Explicity enable/disable DMA for a
+ * particular memory window.
+ */
+ DOMAIN_ATTR_ENABLE,
};
Whitespace
-Scott
--
To
struct device_domain_info, link);
> + remove_domain_ref(info, dma_domain->subwin_cnt);
> + }
I wonder if you should use list_for_each_safe() instead.
The above is simpler if you're destroying the entire list.
> +}
> +
> +static int configure_domain_
On 12/10/2012 04:10:06 AM, Sethi Varun-B16395 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, December 04, 2012 11:53 PM
> To: Sethi Varun-B16395
> Cc: Wood Scott-B07421; Joerg Roedel; linux-kernel@vger.kernel.org;
> io...@lists.linux-founda
)
powerpc-allyesconfig
It's been over 3 years since powerpc-allyesconfig built (it's just too
big for the relocation model the kernel uses) -- how is this a
regression?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
API.
3. Added an attribute for enabling/disabling DMA to a particular
memory window.
Signed-off-by: Varun Sethi
---
changes in v4:
- Updated comment explaining subwindows(as mentioned by Scott).
change in v3:
-renamed the stash attribute targets
include/linux/iommu.h | 36
. Are there any major "philosophical" barriers to including this sort
of thing in the Kernel?
3. Do you have any advice?
Thanks,
-Scott
Intro
==
ASLRX, or Address Space Layout Randomization Extreme
Stack trace is here: http://www.flickr.com/photos/94373754@N06/8662259093/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordom
Is this easy to reproduce? Do you know whether the same thing happens
> with an upstream kernel, e.g., v3.8 or v3.9-rc7? If it turns out that
> this bug still exists in the upstream kernel, Zhang will probably be
> interested in it.
It isn't easy to simulate. It only happened to me one. I'll file
,
DOMAIN_ATTR_WINDOWS,
+ DOMAIN_ATTR_PAMU_STASH,
+ DOMAIN_ATTR_PAMU_ENABLE,
+ DOMAIN_ATTR_FSL_PAMUV1,
DOMAIN_ATTR_MAX,
Please be consistent on whether "PAMU" gets an "FSL_" namespace prefix
(I'd prefer that it does).
-Scott
--
To unsubscribe from this list: s
The device tree binding will also need to be fixed to note the
difference in "reg" between "fsl,gianfar-mdio" and "fsl-gianfar-tbi" --
and should give an example of the latter.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&q
On 06/12/2013 03:19:30 AM, Rojhalat Ibrahim wrote:
On Tuesday 11 June 2013 12:28:59 Scott Wood wrote:
> Yes, I figured it was non-PCIe because the code change that you said
> helped was on the non-PCIe branch of the if/else. Generally it's
good
> to explicitly mention the chi
On 06/13/2013 02:21:24 AM, Rojhalat Ibrahim wrote:
On Wednesday 12 June 2013 16:50:26 Scott Wood wrote:
> On 06/12/2013 03:19:30 AM, Rojhalat Ibrahim wrote:
> > On Tuesday 11 June 2013 12:28:59 Scott Wood wrote:
> > > Yes, I figured it was non-PCIe because the code chan
setup_indirect_pci for all
device types.
fsl_indirect_read_config is now only used for booke/86xx PCIe
controllers.
Reported-by: Michael Guntsche
Cc: Scott Wood
Signed-off-by: Rojhalat Ibrahim
---
v2: Make it more consistent.
arch/powerpc/sysdev/fsl_pci.c | 20 +++-
1 file
ave holes in an "interrupts" property, propose
something non-hacky on devicetree-disc...@lists.ozlabs.org.
Or, do what some other devices do, and have a different property that
indicates which pins are connected, and only include those in the
"interrupts" property. Se
On 06/17/2013 08:15:33 AM, Rojhalat Ibrahim wrote:
On Friday 14 June 2013 15:18:03 Scott Wood wrote:
> On 83xx:
> cc1: warnings being treated as errors
>
/home/scott/fsl/git/linux/upstream/arch/powerpc/sysdev/fsl_pci.c:100:23:
> error: 'fsl_indirect_pcie_ops' defined
On 05/28/2013 07:12:32 PM, Alexey Kardashevskiy wrote:
On 05/29/2013 09:35 AM, Scott Wood wrote:
> On 05/28/2013 06:30:40 PM, Alexey Kardashevskiy wrote:
>> >> >>> @@ -939,6 +940,9 @@ struct kvm_s390_ucas_mapping {
>> >> >>> #define KVM_G
On 05/29/2013 06:10:33 PM, Alexey Kardashevskiy wrote:
On 05/30/2013 06:05 AM, Scott Wood wrote:
> On 05/28/2013 07:12:32 PM, Alexey Kardashevskiy wrote:
>> On 05/29/2013 09:35 AM, Scott Wood wrote:
>> > On 05/28/2013 06:30:40 PM, Alexey Kardashevskiy wrote:
>> &g
On 05/29/2013 06:29:13 PM, Alexey Kardashevskiy wrote:
On 05/30/2013 09:14 AM, Scott Wood wrote:
> On 05/29/2013 06:10:33 PM, Alexey Kardashevskiy wrote:
>> On 05/30/2013 06:05 AM, Scott Wood wrote:
>> > But you didn't put it in the same section as
KVM_CREATE_SPAPR_TC
has a
+ controllable clock source should have a "fsl,pmc-handle" property
pointing
+ to the clock node.
Please respond to the feedback given on v1:
http://patchwork.ozlabs.org/patch/147177/
Also indicate, below the ---, what has changed from previous versions.
-Scott
--
To unsubscrib
to be sure. */
> + mod_timer(&wdt_timer, jiffies + HZ * hw_timo_sec / 2);
> + }
> +}
> +
> +static void mpc8xxx_wdt_sw_keepalive(void)
> +{
> + wdt_last_ping = jiffies;
> + mpc8xxx_wdt_timer_ping(0);
> }
This isn't new with this patch,
goto err0;
} else {
- fsl_setup_indirect_pci(hose, rsrc_cfg.start,
+ setup_indirect_pci(hose, rsrc_cfg.start,
rsrc_cfg.start + 4, 0);
}
The only difference here is that you're not setting hose->ops
On 06/11/2013 02:24:28 AM, Rojhalat Ibrahim wrote:
On Monday 10 June 2013 17:52:33 Scott Wood wrote:
> On 06/10/2013 12:07:43 PM, Michael Guntsche wrote:
> > Good evening,
> >
> > This patch does not fix the problem, during boot the kernel still
> > panics. I had a cl
On 06/11/2013 12:09:42 PM, Michael Guntsche wrote:
On Tue, Jun 11, 2013 at 7:00 PM, Scott Wood
wrote:
> On 06/11/2013 02:24:28 AM, Rojhalat Ibrahim wrote:
>>
>> On Monday 10 June 2013 17:52:33 Scott Wood wrote:
>> > On 06/10/2013 12:07:43 PM, Michael Guntsche wr
b/drivers/dma/fsldma.h
@@ -112,10 +112,10 @@ struct fsldma_chan_regs {
};
struct fsldma_chan;
-#define FSL_DMA_MAX_CHANS_PER_DEVICE 4
+#define FSL_DMA_MAX_CHANS_PER_DEVICE 8
struct fsldma_device {
- void __iomem *regs; /* DGSR register base */
+ void __iomem *regs0, *regs1;/* D
On 07/02/2013 10:47:44 PM, Hongbo Zhang wrote:
On 07/03/2013 07:13 AM, Scott Wood wrote:
Wait a second -- how are we even getting into this code on these new
DMA controllers? All 85xx-family DMA controllers use
fsldma_chan_irq directly.
Right, we are using fsldma_chan_irq, this code
100644 arch/powerpc/boot/dts/fsl/qoriq-dma2-1.dtsi
Scott, any comment of these two file names?
There's "dma2" again...
How about elo3-dma-.dtsi?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kerne
gt; + for_each_compatible_node(np, "pci", "fsl,mpc8314-pcie")
> + mpc83xx_add_bridge(np);
> +#endif
Call mpc83xx_setup_pci().
> +static void __init tqm8315_init_IRQ(void)
> +{
> + struct device_node *np;
> +
> + np = of_find_node_by_type(NULL
g size; /* Huge page size (always 16MB at the
moment) */
+};
Shouldn't this be namespaced to something like "book3s" or "spapr"?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vge
New DTS file for Servergy CTS-1000 systems
/home/scott/fsl/git/linux/upstream/.git/rebase-apply/patch:201: space
/before tab in indent.
84 2 0 0
/home/scott/fsl/git/linux/upstream/.git/rebase-apply/patch:873: trailing
whitespace.
On 03/21/2013 09:27:14 AM, Kevin Hilman wrote:
Gleb Natapov writes:
> On Wed, Mar 20, 2013 at 06:58:41PM -0500, Scott Wood wrote:
>> On 03/14/2013 07:13:46 PM, Kevin Hilman wrote:
>> >The new context tracking subsystem unconditionally includes
kvm_host.h
>> >heade
On 03/21/2013 02:16:00 PM, Gleb Natapov wrote:
On Thu, Mar 21, 2013 at 01:42:34PM -0500, Scott Wood wrote:
> On 03/21/2013 09:27:14 AM, Kevin Hilman wrote:
> >Gleb Natapov writes:
> >
> >> On Wed, Mar 20, 2013 at 06:58:41PM -0500, Scott Wood wrote:
> >>>
-- there is now a second reg entry.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
mpc8540-dma", "fsl,eloplus-dma",
"fsl,elo3-dma";
In addition to the above issue about ordering, mpc8540 does not have
elo3.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
genksysms parses this .o, calculates
> the CRCs and writes a linker script that "resolves" the symbols to
> the calc
Scott, can somebody from FSL test that on 32-bit and Ack it ?
Thanks !
Cheers,
Ben.
It boots for me on e500mc and I can insert modules.
-Scott
--
To unsubscribe
On 07/16/2013 07:04:05 PM, Benjamin Herrenschmidt wrote:
On Tue, 2013-07-16 at 17:40 -0500, Scott Wood wrote:
> On 07/15/2013 03:47:06 AM, Benjamin Herrenschmidt wrote:
> > On Mon, 2013-07-15 at 14:04 +1000, Anton Blanchard wrote:
> > > Module CRCs are implemented as absolut
nce between elo3 and
previous chips regarding fsl,CHIP-dma as far as the binding is
concerned.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/major
the same time.
Signed-off-by: Hongbo Zhang
ACK, but next time please do the whitespace fixes as a separate patch
so that it's easier to see what's actually changing.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
+-
5 files changed, 232 insertions(+), 4 deletions(-)
create mode 100644 arch/powerpc/boot/dts/fsl/elo3-dma-0.dtsi
create mode 100644 arch/powerpc/boot/dts/fsl/elo3-dma-1.dtsi
ACK
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
> + }
> + }
> +}
Why are you moving this function? This makes it hardaer to see the
changes you make -- and is likely the cause of unintended changes being
made due to a bad conflict resolution. In particular, you seem to be
reverting commit 13635dfdc6aa8d2890e02dc441d
I've got it in my queue that I hope to send soon.
-Scott
On 07/31/2013 09:45:25 AM, Ian Campbell wrote:
ping?
On Fri, 2013-05-31 at 11:14 +0100, Ian Campbell wrote:
> This file is a common include for B4860 and B4420 but is not a
valid DTS itself:
> DTC arch/powerpc/boo
the device tree that we do this translation at all,
versus having an empty ranges and using CCSR offsets in the children.
It's not about translating between the DMA controller's view and the
CPU's view or anything like that.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The binding should
mention it if it has particular requirements for the value of either
property, but I don't think we care here (much like we don't care what
sort of translation is used in ranges).
> Perhaps they're considered such a core part of DT functionality that it'
probably s/registers mapping/register specifier/ as well.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 2013-08-21 at 17:15 -0600, Stephen Warren wrote:
> On 08/21/2013 04:57 PM, Scott Wood wrote:
> > On Wed, 2013-08-21 at 16:40 -0600, Stephen Warren wrote:
> >> On 07/29/2013 04:49 AM, hongbo.zh...@freescale.com wrote:
>
> >>> +- ranges: describe
1 - 100 of 2498 matches
Mail list logo
