On Sat, Jul 05, 2008 at 11:26:24AM +1000, David Gibson wrote:
> On Sat, Jul 05, 2008 at 01:12:31AM +0200, Segher Boessenkool wrote:
> >>> /* deprecated; */
> >>> device_type = "i2c";
> >>
> >> How about "deprecated but kept for compatibility with true Open
> >> Firmware
> >> implementations"?
On Sat, 2008-07-05 at 15:43 +1000, Michael Ellerman wrote:
> > The current Cell IOMMU implementation sets the IOPTE_SO_RW bits in all
> > IOTPEs
> > (for both the dynamic and fixed mappings) which enforces strong ordering of
> > both reads and writes. This patch makes the default behaviour weak or
On Fri, 2008-07-04 at 21:05 +0200, [EMAIL PROTECTED] wrote:
> Introduce a new dma attriblue DMA_ATTR_STRONG_ORDERING to use strong ordering
> on DMA mappings in the Cell processor. Add the code to the Cell's IOMMU
> implementation to use this.
>
> The current Cell IOMMU implementation sets the IO
On Jul 3, 2008, at 1:34 PM, Grant Likely wrote:
How about splitting up like this:
Documentation/powerpc/device-tree/fsl/cpm.txt
Documentation/powerpc/device-tree/fsl/cpm/uart.txt
Documentation/powerpc/device-tree/fsl/tsec.txt
Documentation/powerpc/device-tree/interrupts.txt
Documentation/power
On Jul 3, 2008, at 6:20 PM, Nathan Lynch wrote:
Beginning with Power6, there is a set of 32 PMU events which is
compatible across POWER processor lines. PPC_FEATURE_PMU_COMPAT
indicates support for this subset.
The PMU isn't, as far as I know, part of the architecture, it's up to
each imple
On Fri, Jul 04, 2008 at 07:03:25AM -0400, Timur Tabi wrote:
>> [EMAIL PROTECTED] { // PSC2
>> compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s";
>> cell-index = <1>;
>
> cell-index should be zero-based, not one-based.
Well...since cell-index is fo
On Sat, Jul 05, 2008 at 01:12:31AM +0200, Segher Boessenkool wrote:
>>> /* deprecated; */
>>> device_type = "i2c";
>>
>> How about "deprecated but kept for compatibility with true Open
>> Firmware
>> implementations"?
>
> Well, except a flat tree isn't compatible with OF at all here.
> A
On Fri, Jul 04, 2008 at 03:01:00PM -0700, Andrew Morton wrote:
> (heck, let's cc lkml - avoid having to go through all this again)
>
> It would be excellent if gcc had an extension system so that you could
> add new printf control chars and maybe even tell gcc how to check them.
> But of course, i
On Fri, Jul 4, 2008 at 2:49 PM, Mark Brown
<[EMAIL PROTECTED]> wrote:
> On Tue, Jul 01, 2008 at 05:53:40PM -0600, Grant Likely wrote:
>> + /* Tell the of_soc helper about this codec */
>> + of_snd_soc_register_codec(&aic26_soc_codec_dev, aic26, &aic26_dai,
>> +
On Fri, Jul 4, 2008 at 5:36 PM, Segher Boessenkool
<[EMAIL PROTECTED]> wrote:
>> +The SPI master node requires the following properties:
>> +- #address-cells - number of cells required to define a chip select
>> + address on the SPI bus.
>
> Hrm. Should this (and "re
+The SPI master node requires the following properties:
+- #address-cells - number of cells required to define a chip
select
+ address on the SPI bus.
Hrm. Should this (and "reg" in the child node) be required for SPI
masters that have only one chip select?
+
On Sat, 5 Jul 2008, Benjamin Herrenschmidt wrote:
>
> I'll give it a try using probe_kernel_address() instead on monday.
Here's the updated patch which uses probe_kernel_address() instead (and
moves the whole #ifdef mess out of the code that wants it and into a
helper function - and maybe we
I'm sure you'll hate for doing this,
No, it's an excellent move :-)
but I've asked Kim to create a new
Documentation/powerpc/fsl-device-tree-bindings.txt as part of his SEC
patch.
As a separate patch, that (at first) _only_ moves the content into
separate
files, please.
Segher
/* deprecated; */
device_type = "i2c";
How about "deprecated but kept for compatibility with true Open
Firmware
implementations"?
Well, except a flat tree isn't compatible with OF at all here.
A "device_type" promises a certain interface; a flat tree doesn't
even have the "op
On Fri, 2008-07-04 at 13:02 -0700, Linus Torvalds wrote:
>
> That function descriptor indirection is totally untested, and I did it
> with a
>
> pagefault_disable();
> __get_user(..)
> pagefault_enable();
>
> thing because I thought it would be nice if printk() was alway
Just curious... why we're maintaining documentation in the .txt file?
Because it is human-readable text?
Or is this too wild? :-)
Yes :-)
Segher
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-d
> u64 is easy to fix, and I don't know why we haven't. Just make it
> unsigned long long on all architectures.
Yup. Also, one of the major user of that is to print a struct resource,
which everybody does differently, so we may even look at doing a %pR
that does the nice start..end [attr]..
Ben.
+- compatible : Should contain entries for this and backward compatible
+ SEC versions, high to low, e.g., "fsl,sec2.1", "fsl,sec2.0"
First entry should state the _exact_ version of the device. "sec-N.M"
isn't good enough; there can be implementation bugs.
There can be more entries; you make
Please point out any patches that have been posted but havent made it
into a git tree related to Freescale chips.
I haven't heard back from Segher, so:
http://patchwork.ozlabs.org/linuxppc/patch?id=19313
You haven't heard back because I feel like I'm talking to a wall.
The "compatible" defin
(heck, let's cc lkml - avoid having to go through all this again)
On Fri, 4 Jul 2008 14:42:53 -0600 Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 04, 2008 at 01:27:16PM -0700, Andrew Morton wrote:
> > On Fri, 4 Jul 2008 13:02:05 -0700 (PDT) Linus Torvalds <[EMAIL PROTECTED]>
> > wrote
On Tue, Jul 01, 2008 at 05:53:40PM -0600, Grant Likely wrote:
> +static ssize_t aic26_keyclick_show(struct device *dev,
> +struct device_attribute *attr, char *buf)
> +{
> + struct aic26 *aic26 = dev_get_drvdata(dev);
> + int val, amp, freq, len;
> +
> +
On Fri, Jul 04, 2008 at 01:27:16PM -0700, Andrew Morton wrote:
> On Fri, 4 Jul 2008 13:02:05 -0700 (PDT) Linus Torvalds <[EMAIL PROTECTED]>
> wrote:
> > > so I think we could easily just say that we extend %p in various ways:
> > >
> > > - %pS - print pointer as a symbol
> > >
> > > and leave t
On Fri, 4 Jul 2008, Andrew Morton wrote:
>
> probe_kernel_address() should be usable here.
Right you are.
> > +static char *string(char *buf, char *end, char *s, int field_width, int
> > precision, int flags)
> > +{
> > + int len, i;
> > +
> > + if ((unsigned long)s < PAGE_SIZE)
> > +
On Fri, Jul 04, 2008 at 01:02:05PM -0700, Linus Torvalds wrote:
> On Fri, 4 Jul 2008, Linus Torvalds wrote:
> >
> > so I think we could easily just say that we extend %p in various ways:
> >
> > - %pS - print pointer as a symbol
> >
> > and leave tons of room for future extensions for different
On Fri, 4 Jul 2008 13:02:05 -0700 (PDT) Linus Torvalds <[EMAIL PROTECTED]>
wrote:
>
>
> On Fri, 4 Jul 2008, Linus Torvalds wrote:
> >
> > so I think we could easily just say that we extend %p in various ways:
> >
> > - %pS - print pointer as a symbol
> >
> > and leave tons of room for futur
On Fri, 4 Jul 2008, Linus Torvalds wrote:
>
> so I think we could easily just say that we extend %p in various ways:
>
> - %pS - print pointer as a symbol
>
> and leave tons of room for future extensions for different kinds of
> pointers.
So here's a totally untested example patch of this,
This patch adds a cpufreq governor that takes the number of running spus
into account. It's very similar to the ondemand governor, but not as complex.
Instead of hacking spu load into the ondemand governor it might be easier to
have cpufreq accepting multiple governors per cpu in future.
Don't know
Axonram module registers one block device for each DDR2 DIMM found
on a system. This means that each DDR2 DIMM becomes its own block device
major number. This patch lets axonram module to register the only one
block device for all DDR2 DIMMs which also spares kernel resources.
Signed-off-by: Maxim
Make iommu_map_sg take a struct iommu_table. It did so before commit
740c3ce66700640a6e6136ff679b067e92125794 (iommu sg merging: ppc: make
iommu respect the segment size limits).
This stops the function looking in the archdata.dma_data for the iommu
table because in the future it will be called wi
Update iommu_alloc() to take the struct dma_attrs and pass them on to
tce_build(). This change propagates down to the tce_build functions of
all the platforms.
Signed-off-by: Mark Nelson <[EMAIL PROTECTED]>
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/iommu.c
Hi Paul and Ben,
These are the cell related patches I would like to see in
2.6.27. If there are no further comments, please pull into
powerpc-next from
master.kernel.org/pub/scm/linux/kernel/git/arnd/cell-2.6.git cell-next
--
___
Linuxppc-dev mailing
Introduce a new dma attriblue DMA_ATTR_STRONG_ORDERING to use strong ordering
on DMA mappings in the Cell processor. Add the code to the Cell's IOMMU
implementation to use this.
The current Cell IOMMU implementation sets the IOPTE_SO_RW bits in all IOTPEs
(for both the dynamic and fixed mappings)
Move device_to_mask() to dma-mapping.h because we need to use it from
outside dma_64.c in a later patch.
Signed-off-by: Mark Nelson <[EMAIL PROTECTED]>
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/dma_64.c |9 -
include/asm-powerpc/dma-mapping.h |9
As nr_active counter includes also spus waiting for syscalls to return
we need a seperate counter that only counts spus that are currently running
on spu side. This counter shall be used by a cpufreq governor that targets
a frequency dependent from the number of running spus.
From: Maxim Shchetyni
Update powerpc to use the new dma_*map*_attrs() interfaces. In doing so
update struct dma_mapping_ops to accept a struct dma_attrs and propagate
these changes through to all users of the code (generic IOMMU and the
64bit DMA code, and the iseries and ps3 platform code).
The old dma_*map_*() interf
DDR2 memory DIMMs on the Axon could be accessed only as one partition
when using file system drivers which are using the direct_access() method.
This patch enables for such file system drivers to access Axon's DDR2 memory
even if it is splitted in several partitions.
Signed-off-by: Maxim Shchetyni
Make cell_dma_dev_setup_iommu() return a pointer to the struct iommu_table
(or NULL if no table can be found) rather than putting this pointer into
dev->archdata.dma_data (let the caller do that), and rename this function
to cell_get_iommu_table() to reflect this change.
This will allow us to get
This patch adds support for the power button on future IBM cell blades.
It actually doesn't shut down the machine. Instead it exposes an
input device /dev/input/event0 to userspace which sends KEY_POWER
if power button has been pressed.
haldaemon actually recognizes the button, so a plattform indep
On 7/4/08, Grant Likely <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 04, 2008 at 06:35:39PM +0200, Andre Schwarz wrote:
> > + #address-cells = <2>;
> > + #size-cells = <1>;
> > + ranges = <0x0 0x0 0xff80 0x0080>;
> > + [EMAIL PROTECTED],0 {
>
Hi Josh,
Here are the bulk of the Xilinx 440 support patches. Please pull
into your next branch.
Thanks,
g.
The following changes since commit f3e909c2750eb20536bacacc867dc9047b70546a:
Michael Neuling (1):
powerpc: Update for VSX core file and ptrace
are available in the git reposito
On Fri, Jul 04, 2008 at 06:35:39PM +0200, Andre Schwarz wrote:
> The mvBlueCOUGAR-P is a MPC5200B based camera system with Intel Gigabit
> ethernet
> controller (using e1000). It's just another MPC5200_simple board.
>
> Signed-off-by: Andre Schwarz <[EMAIL PROTECTED]>
> ---
>
>
> Grant,
>
> I
This patch adds few bindings for the new drivers to be submitted through
the appropriate maintainers.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
---
Updated to decrypt MCU, and to split the bindings into appropriate files.
.../powerpc/device-tree/fsl/mcu-mpc8349emitx.txt | 17 ++
The mvBlueCOUGAR-P is a MPC5200B based camera system with Intel Gigabit ethernet
controller (using e1000). It's just another MPC5200_simple board.
Signed-off-by: Andre Schwarz <[EMAIL PROTECTED]>
---
Grant,
I don't know if there are any merge windows ...
If the patch should be modified or re-su
On Fri, Jul 04, 2008 at 05:10:46PM +0200, Andre Schwarz wrote:
> I removed GPIO Lib and the problem is gone.
> I'm not yet using it anyway under linux - they're mainly for system
> configuration (setting up muxes etc.).
>
> I'll dig into it when I have some time.
When you do, try adding "#define
On Fri, Jul 04, 2008 at 09:04:42PM +1000, Paul Mackerras wrote:
> This updates the MAINTAINERS entries for powerpc. It adds Ben H to
> the overall Linux for PowerPC entry and makes it clear this covers
> both 32-bit and 64-bit machines. It removes the separate entry we had
> for Linux on 64-bit
Grant Likely schrieb:
> On Fri, Jul 04, 2008 at 11:57:14AM +0200, Andre Schwarz wrote:
>
>> Sascha, Grant,
>>
>> I'm running on 2.6.26-rc6 with an MPC5200B based system.
>>
>> Looks like some (for me) crucial GPIO are touched during boot.
>> Is this possible ?
>>
>> Of course I have compiled in
On Fri, Jul 04, 2008 at 07:03:25AM -0400, Timur Tabi wrote:
>> [EMAIL PROTECTED] { // PSC2
>> compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s";
>> cell-index = <1>;
>
> cell-index should be zero-based, not one-based.
>
Umm... this is for PSC #2..
On Fri, Jul 04, 2008 at 11:57:14AM +0200, Andre Schwarz wrote:
> Sascha, Grant,
>
> I'm running on 2.6.26-rc6 with an MPC5200B based system.
>
> Looks like some (for me) crucial GPIO are touched during boot.
> Is this possible ?
>
> Of course I have compiled in GPIO-Lib and specified the GPIOs i
On Jul 3, 2008, at 6:20 PM, Nathan Lynch wrote:
Beginning with Power6, there is a set of 32 PMU events which is
compatible across POWER processor lines. PPC_FEATURE_PMU_COMPAT
indicates support for this subset.
Signed-off-by: Nathan Lynch <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/cputable.c
Anton Vorontsov wrote:
On Thu, Jul 03, 2008 at 01:20:18PM -0500, Kumar Gala wrote:
Guys,
/* deprecated; */
device_type = "i2c";
How about "deprecated but kept for compatibility with true Open Firmware
implementations"?
Seriously, you can't have a binding for "OF" and then cu
From: Nathan Fontenot <[EMAIL PROTECTED]>
Update the architecture vector to indicate that Cooperative Memory
Overcommitment is supported.
This is the last patch in the series. Committing it will signal to
the platform firmware is CMO enabled.
Signed-off-by: Nathan Fontenot <[EMAIL PROTECTED]>
From: Robert Jennings <[EMAIL PROTECTED]>
Enable the driver to function in a Cooperative Memory Overcommitment (CMO)
environment.
The following changes are made to enable the driver for CMO:
* DMA mapping errors will not result in error messages if entitlement has
been exceeded and resources
Enable ibmveth for Cooperative Memory Overcommitment (CMO). For this driver
it means calculating a desired amount of IO memory based on the current MTU
and updating this value with the bus when MTU changes occur. Because DMA
mappings can fail, we have added a bounce buffer for temporary cases whe
From: Santiago Leon <[EMAIL PROTECTED]>
Activates larger rx buffer pools when the MTU is changed to a larger
value. This patch de-activates the large rx buffer pools when the MTU
changes to a smaller value.
Signed-off-by: Santiago Leon <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAIL P
From: Nathan Fontenot <[EMAIL PROTECTED]>
Verify memory entitlement updates can be handled by vio.
Signed-off-by: Nathan Fontenot <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/lparcfg.c | 10 ++
1 file changed, 10 insertions(+)
Index:
From: Robert Jennings <[EMAIL PROTECTED]>
This is a large patch but the normal code path is not affected. For
non-pSeries platforms the code is ifdef'ed out and for non-CMO enabled
pSeries systems this does not affect the normal code path. Devices that
do not perform DMA operations do not need m
To support Cooperative Memory Overcommitment (CMO), we need to check
for failure from some of the tce hcalls.
These changes for the pseries platform affect the powerpc architecture;
patches for the other affected platforms are included in this patch.
pSeries platform IOMMU code changes:
* platfo
From: Brian King <[EMAIL PROTECTED]>
With the addition of Cooperative Memory Overcommitment (CMO) support
for IBM Power Systems, two fields have been added to the VPA to report
paging statistics. Add support in lparcfg to report them to userspace.
Signed-off-by: Brian King <[EMAIL PROTECTED]>
Sig
From: Brian King <[EMAIL PROTECTED]>
The Cooperative Memory Overcommit (CMO) on System p does not currently
support native PCI devices or eBus devices when enabled. Prevent
PCI bus probe and eBus device probe if the feature is enabled.
Signed-off-by: Brian King <[EMAIL PROTECTED]>
Signed-off-by:
From: Brian King <[EMAIL PROTECTED]>
Adds a collaborative memory manager, which acts as a simple balloon driver
for System p machines that support cooperative memory overcommitment
(CMO).
Signed-off-by: Brian King <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAIL PROTECTED]>
---
arch/
From: Brian King <[EMAIL PROTECTED]>
Newer versions of firmware support page states, which are used by the
collaborative memory manager (future patch) to "loan" pages to the
hypervisor for use by other partitions.
Signed-off-by: Brian King <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAI
From: Brian King <[EMAIL PROTECTED]>
Newer versions of firmware support page states, which are used by the
collaborative memory manager (future patch) to "loan" pages to the
hypervisor for use by other partitions.
Signed-off-by: Brian King <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAI
From: Robert Jennings <[EMAIL PROTECTED]>
For Cooperative Memory Overcommitment (CMO), set the FW_FEATURE_CMO
flag in powerpc_firmware_features from the rtas ibm,get-system-parameters
table prior to calling iommu_init_early_pSeries.
With this, any CMO specific functionality can be controlled by c
From: Robert Jennings <[EMAIL PROTECTED]>
For Cooperative Memory Overcommitment (CMO), set the FW_FEATURE_CMO
flag in powerpc_firmware_features from the rtas ibm,get-system-parameters
table prior to calling iommu_init_early_pSeries.
With this, any CMO specific functionality can be controlled by c
From: Nathan Fontenot <[EMAIL PROTECTED]>
Split the retrieval of processor entitlement data returned in the H_GET_PPP
hcall into its own helper routine.
Signed-off-by: Nathan Fontenot <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/lparcfg.c | 80
From: Nathan Fontenot <[EMAIL PROTECTED]>
Update /proc/ppc64/lparcfg to enable displaying of Cooperative Memory
Overcommitment statistics as reported by the H_GET_MPP hcall. This also
updates the lparcfg interface to allow setting memory entitlement and
weight.
Signed-off-by: Nathan Fontenot <[E
From: Nathan Fotenot <[EMAIL PROTECTED]>
Split the retrieval and setting of processor entitlement and weight into
helper routines. This also removes the printing of the raw values
returned from h_get_ppp, the values are already parsed and printed.
Signed-off-by: Nathan Fontenot <[EMAIL PROTECTED
From: Nathan Fontenot <[EMAIL PROTECTED]>
Remove the extraneous error reporting used when a hcall made from lparcfg fails.
Signed-off-by: Nathan Fontenot <[EMAIL PROTECTED]>
Signed-off-by: Robert Jennings <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/lparcfg.c | 32 -
This is version 3 of the full patchset. Please consider this for 2.6.27.
Only the vio bus patch is changed but with two other patches dropped I
felt it would be clearer to post the full set.
A change was made so that devices not performing DMA operations will not
require modification, therefore t
Laurent Pinchart wrote:
The restart() function is called when the link state changes and resets
multicast and promiscuous settings. This patch restores those settings at the
end of restart().
Signed-off-by: Laurent Pinchart <[EMAIL PROTECTED]>
---
drivers/net/fs_enet/mac-fcc.c |3 +++
1 fil
Stefan Roese wrote:
From: Sathya Narayanan <[EMAIL PROTECTED]>
Short packets has to be discarded by the driver. So this patch addresses the
issue of discarding the short packets of size lesser then ethernet header
size.
Signed-off-by: Sathya Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Stefan R
Stefan Roese wrote:
From: Sathya Narayanan <[EMAIL PROTECTED]>
The descriptor pointers were not initialized to NIL values, so it was
poiniting to some random addresses which was completely invalid. This
fix takes care of initializing the descriptor to NIL values and clearing
the valid descriptor
Jan-Bernd Themann wrote:
A mutex has to be replaced by spinlocks as it can be called from
a context which does not allow sleeping.
The kzalloc flag GFP_KERNEL has to be replaced by GFP_ATOMIC
for the same reason.
Signed-off-by: Jan-Bernd Themann <[EMAIL PROTECTED]>
applied 1-3 to 2.6.26
Michael Neuling writes:
> + /*
> + * If userspace doesn't provide enough room for VSX data,
> + * but current thread has used VSX, we don't have anywhere
> + * to store the full context back into.
> + */
> + ((ctx_size < sizeof(struct ucontex
This updates the MAINTAINERS entries for powerpc. It adds Ben H to
the overall Linux for PowerPC entry and makes it clear this covers
both 32-bit and 64-bit machines. It removes the separate entry we had
for Linux on 64-bit PowerPC where Anton and I were listed as
maintainers - Anton hasn't been
On Jul 3, 2008, at 12:33 PM, Grant Likely wrote:
Yes, but you hadn't written these functions when I wrote this helper.
:-P. I believe ASoC v2 makes all this stuff unnecessary, but I'm
waiting for v2 to hit mainline before I port forward.
FYI, it took me about a month to port my drivers to AS
[EMAIL PROTECTED] { // PSC2
compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s";
cell-index = <1>;
cell-index should be zero-based, not one-based.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozl
On Jun 30, 2008, at 4:24 PM, Andrew Morton wrote:
This is also incorrect. We cannot pass u64 or uint64_t into printk at
all. We do not know what type the architectures uses to implement
them. It should be cast to a known type. In this case `unsigned long
long'.
Ok, I'll fix these, but I'm
Sascha, Grant,
I'm running on 2.6.26-rc6 with an MPC5200B based system.
Looks like some (for me) crucial GPIO are touched during boot.
Is this possible ?
Of course I have compiled in GPIO-Lib and specified the GPIOs in the dts.
But no access yet - I'd like to preserve the setup from u-boot...
r
When the ucontext changed to add the VSX context, this broke backwards
compatibly on swapcontext. swapcontext only compares the ucontext
size passed in from the user to the new kernel ucontext size.
This adds a check against the old ucontext size (with VMX but without
VSX). It also adds some san
Hi Anton,
Anton Vorontsov wrote:
This patch adds few bindings for the new drivers to be submitted through
the appropriate maintainers.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
---
Segher, thanks for the comments on the previous version. Do you see any
issues with this one or anything
On Thu, 3 Jul 2008 23:54:26 -0600, Grant Likely wrote:
> On Thu, Jul 3, 2008 at 9:24 AM, Grant Likely <[EMAIL PROTECTED]> wrote:
> > On Thu, Jul 03, 2008 at 08:22:18AM -0400, Jon Smirl wrote:
> >> Testing was good when the patch was initially posted in January. In
> >> the last six months the initi
82 matches
Mail list logo
