> -Original Message-
> From: Zang Roy-R61911
> Sent: Wednesday, August 11, 2010 12:47 PM
> To: Zang Roy-R61911; a...@linux-foundation.org;
> linux-...@vger.kernel.org
> Cc: linuxppc-...@ozlabs.org; mir...@gmail.com;
> cbouatmai...@gmail.com; grant.lik...@secretlab.ca
> Subject: RE: [P
> --
> > Date: Thu, 12 Aug 2010 13:53:51 -0400
> > From: Jeff Angielski
> > To: linuxppc-dev@lists.ozlabs.org
> > Subject: Re: Query regarding 2.6.335 RT[Ingo's] and Non-RT performance
> > Message-ID: <4c64352f.4090...@theptrgroup.com>
> > Conten
Josh,
This one looks okay to me, but I've left it for you to comment on. I
haven't seen any comments, so should I go ahead and pick it up for my
2.6.37 -next branch?
Cheers,
g.
On Fri, Aug 13, 2010 at 10:09 PM, Sergey Temerkhanov
wrote:
> This patch enables support for Xilinx Virtex 4 FX singe
On Wed, Aug 11, 2010 at 08:56:03PM +0400, Anton Vorontsov wrote:
> Marvell and GPIO bindings live in their own files, so the TOC should not
> mention them.
>
> Also fix chapters numbering.
>
> Signed-off-by: Anton Vorontsov
Applied, thanks.
g.
> ---
> Documentation/powerpc/booting-without-of
On Monday 16 August 2010 21:00:03 Richard Cochran wrote:
>
> On Mon, Aug 16, 2010 at 04:26:23PM +0200, Arnd Bergmann wrote:
> > Have you considered integrating the subsystem into the Posix clock/timer
> > framework?
>
> Yes, but see below.
>
> > I can't really tell from reading the source if th
On Mon, Aug 16, 2010 at 12:24 PM, john stultz wrote:
> On Mon, Aug 16, 2010 at 4:17 AM, Richard Cochran
> A few comments below
>
>> +** PTP user space API
>> +
>> + The class driver creates a character device for each registered PTP
>> + clock. User space programs may control the clock usi
On Mon, Aug 16, 2010 at 4:17 AM, Richard Cochran
wrote:
> This patch adds an infrastructure for hardware clocks that implement
> IEEE 1588, the Precision Time Protocol (PTP). A class driver offers a
> registration method to particular hardware clock drivers. Each clock is
> exposed to user space a
On Mon, Aug 16, 2010 at 04:26:23PM +0200, Arnd Bergmann wrote:
> Have you considered integrating the subsystem into the Posix clock/timer
> framework?
Yes, but see below.
> I can't really tell from reading the source if this is possible or
> not, but my feeling is that if it can be done, that wo
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > + rio_mport_write_config_32(mport, destid, hopcount,
> > + LOCAL_RTE_CONF_DESTID_SEL, table);
> > +
> > + for (i = 0x8000; i <= 0x80ff;) {
> > + rio_mport_write_config_32(mport, destid, hopcoun
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > This set of RapidIO patches adds support for new IDT Gen2 sRIO
switch
> > devices - CPS-1848 and CPS-1616.
> > Adding these sRIO switches required to implement standard error
recovery
> > mechanism defined by the RapidIO specification.
>
> Th
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > Add check if PW message source device is accessible and change PW
message
> > handler to recover if PW message source device is not available
anymore (power
> > down or link disconnect).
>
> I am not quite sure what the point is of this patch
> Date: Thu, 12 Aug 2010 13:53:51 -0400
> From: Jeff Angielski
> To: linuxppc-dev@lists.ozlabs.org
> Subject: Re: Query regarding 2.6.335 RT[Ingo's] and Non-RT performance
> Message-ID: <4c64352f.4090...@theptrgroup.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 08/11/20
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > - if (!rdev->rswitch)
> > - goto out;
> > -
>
> Is it safe? All devices have a switch?
Yes. Because end-points should not have the "routes" attribute at all
(corrected by this patch).
>
> > @@ -63,10 +59,11 @@ struct device_att
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > - Rearranged RIO port-write interrupt handling to perform message
buffering
> > as soon as possible.
>
> I don't understand this comment: you still schedule work to read the
> port-write queue; so how is this message buffering performed as so
On Mon, Aug 16, 2010 at 05:52:41PM +0530, Ravi Gupta wrote:
> Hi,
>
> I have defined a header file for ioctls macros definitions. I am including
> it in both, my user space application as well as in my device driver. Now
> there are some macros that I want to be visible only in device drive and
>
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > +
> > + if (err_status & RIO_PORT_N_ERR_STS_PW_OUT_ES) {
> > + pr_debug("RIO_EM: servicing Output Error-Stopped
state\n");
> > + /*
> > +* Send a Link-Request/Input-Status control symbol
> > +*/
>
On 08/12/2010 02:08 PM, Andrew Morton wrote:
> On Mon, 09 Aug 2010 12:53:00 -0500
> Nathan Fontenot wrote:
>
>> This set of patches de-couples the idea that there is a single
>> directory in sysfs for each memory section. The intent of the
>> patches is to reduce the number of sysfs directories
On Monday 16 August 2010, Richard Cochran wrote:
> This patch adds an infrastructure for hardware clocks that implement
> IEEE 1588, the Precision Time Protocol (PTP). A class driver offers a
> registration method to particular hardware clock drivers. Each clock is
> exposed to user space as a char
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > Create back and forward links between RIO devices. These links are
intended for
> > use by error management and hot-plug extensions.
>
> As RapidIO is a switched network, the concept of 'previous' and 'next'
> devices is invalid. Perhaps it's
Micha Nelissen wrote:
>
> Alexandre Bounine wrote:
> > A switch ingress port number has to be saved for software assisted
error
> > recovery from the error-stopped state. Saving this information also
allows
> > to remove several register reads from the RIO enumeration process.
>
> Why not keep us
On 06.08.2010, at 18:28, Kumar Gala wrote:
>
> On Jul 29, 2010, at 7:47 AM, Alexander Graf wrote:
>
>> [without]
>>
>> debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /dev/null;
>> done
>>
>> real0m14.659s
>> user0m8.967s
>> sys 0m5.688s
>>
>> [with]
>>
>> debia
Hi,
I have defined a header file for ioctls macros definitions. I am including
it in both, my user space application as well as in my device driver. Now
there are some macros that I want to be visible only in device drive and
some only in user space application. Is there any set of macros defined
Alexandre Bounine wrote:
+ rio_mport_write_config_32(mport, destid, hopcount,
+ LOCAL_RTE_CONF_DESTID_SEL, table);
+
+ for (i = 0x8000; i <= 0x80ff;) {
+ rio_mport_write_config_32(mport, destid, hopcount,
+ RI
Alexandre Bounine wrote:
This set of RapidIO patches adds support for new IDT Gen2 sRIO switch
devices - CPS-1848 and CPS-1616.
Adding these sRIO switches required to implement standard error recovery
mechanism defined by the RapidIO specification.
This is not 'Gen2' specific, as these error ma
Alexandre Bounine wrote:
Add check if PW message source device is accessible and change PW message
handler to recover if PW message source device is not available anymore (power
down or link disconnect).
I am not quite sure what the point is of this patch. What do you need to
recover from?
Alexandre Bounine wrote:
- if (!rdev->rswitch)
- goto out;
-
Is it safe? All devices have a switch?
@@ -63,10 +59,11 @@ struct device_attribute rio_dev_attrs[] = {
__ATTR_RO(asm_did),
__ATTR_RO(asm_vid),
__ATTR_RO(asm_rev),
- __ATTR_RO(routes)
Alexandre Bounine wrote:
- Rearranged RIO port-write interrupt handling to perform message buffering
as soon as possible.
I don't understand this comment: you still schedule work to read the
port-write queue; so how is this message buffering performed as soon as
possible?
- Modified to dis
Alexandre Bounine wrote:
A switch ingress port number has to be saved for software assisted error
recovery from the error-stopped state. Saving this information also allows
to remove several register reads from the RIO enumeration process.
Why not keep using the swpinfo field, as you can extrac
Alexandre Bounine wrote:
+
+ if (err_status & RIO_PORT_N_ERR_STS_PW_OUT_ES) {
+ pr_debug("RIO_EM: servicing Output Error-Stopped state\n");
+ /*
+* Send a Link-Request/Input-Status control symbol
+*/
+
+ /* Read from
Alexandre Bounine wrote:
Create back and forward links between RIO devices. These links are intended for
use by error management and hot-plug extensions.
As RapidIO is a switched network, the concept of 'previous' and 'next'
devices is invalid. Perhaps it's just the way they were
discovered/e
This patch adds support for the PTP clock found on the DP83640.
The basic clock operations and one external time stamp have
been implemented.
Signed-off-by: Richard Cochran
---
drivers/net/phy/Kconfig | 29 ++
drivers/net/phy/Makefile |1 +
drivers/net/phy/dp83640.c | 904 +
This patch adds a driver for the hardware time stamping unit found on the
IXP465. The basic clock operations and an external trigger are implemented.
Signed-off-by: Richard Cochran
---
arch/arm/mach-ixp4xx/include/mach/ixp46x_ts.h | 78 ++
drivers/net/arm/ixp4xx_eth.c | 1
The eTSEC includes a PTP clock with quite a few features. This patch adds
support for the basic clock adjustment functions, plus two external time
stamps and one alarm.
Signed-off-by: Richard Cochran
---
Documentation/powerpc/dts-bindings/fsl/tsec.txt | 57 +++
arch/powerpc/boot/dts/mpc8313erd
This PTP clock simply uses the NTP time adjustment system calls. The
driver can be used in systems that lack a special hardware PTP clock.
Signed-off-by: Richard Cochran
---
drivers/ptp/Kconfig | 12
drivers/ptp/Makefile|1 +
drivers/ptp/ptp_linux.c | 136
This patch adds an infrastructure for hardware clocks that implement
IEEE 1588, the Precision Time Protocol (PTP). A class driver offers a
registration method to particular hardware clock drivers. Each clock is
exposed to user space as a character device with ioctls that allow tuning
of the PTP clo
Now and again there has been talk on the netdev list of adding PTP
support into Linux. One part of the picture is already in place, the
SO_TIMESTAMPING API for hardware time stamping. This patch set offers
the missing second part needed for complete IEEE 1588 support.
* Why all the CCs?
1. IMHO
I have one NOR flash， sector size is 128k.
I want to make jffs2 filesystem on it to store data.
I have used flash_eraseall -j to format it as jffs2.
But I meet the problem when mount the /dev/mtdblock1.
Thanks for any pointers or ideas.
-sh-2.05b# mount -t jffs2 /dev/mtdblock1 /mnt/jffs
Cowar
On Mon, Aug 16, 2010 at 10:26:56AM +0200, Anatolij Gustschin wrote:
> Commit e32e78c5ee8aadef020fbaecbe6fb741ed9029fd
> (powerpc: fix build with make 3.82) introduced a
> typo in uImage target and broke building uImage:
>
> make: *** No rule to make target `uImage'. Stop.
>
> Signed-off-by: Anat
Commit e32e78c5ee8aadef020fbaecbe6fb741ed9029fd
(powerpc: fix build with make 3.82) introduced a
typo in uImage target and broke building uImage:
make: *** No rule to make target `uImage'. Stop.
Signed-off-by: Anatolij Gustschin
Cc: stable
---
arch/powerpc/Makefile |2 +-
1 files changed,
39 matches
Mail list logo
