Hi Arnd,
On Tue, 2007-07-17 at 03:27 +0200, Arnd Bergmann wrote:
> > +static struct resource m48t59_resources[] = {
> > + {
> > + .start = SBCPQ2_RTC_BASE,
> > + .end= SBCPQ2_RTC_BASE + SBCPQ2_RTC_SIZE - 1,
> > + .flags = IORESOURCE_MEM,
> > + }, {
> > +
On Tue, 17 Jul 2007 13:25:03 +0800
Mark Zhan wrote:
> Hi Vitaly,
>
> When you will send out your 8xx/82xx series patches?
>
As I mentioned, they are not mine but Scott's. And should appear shortly
according to him...
> Thanks
> Mark Zhan
> On Tue, 2007-07-17 at 04:44 +0400, Vitaly Bordug wrote
Roland Dreier <[EMAIL PROTECTED]> wrote on 17.07.2007 05:50:13:
> > > Why the module parameter? Is there any reason a user would want to
> > > turn this off? Or conversely, why is it off by default?
> >
> > We're pretty confident this new feature works, but as with all new
and
> > possib
Hello Roland,
>I still haven't seen much code using the feature or
>even any anecdotal information about the performance impact.
The multiple links performance has been significant improved according to
the prototype IPoIB-UD mode test for eHCA driver esepcially for two links
on the same adap
On Tue, 2007-07-17 at 02:59 +0200, Arnd Bergmann wrote:
> On Monday 16 July 2007, Mark Zhan wrote:
>
> > @@ -96,7 +94,7 @@
> > pvid = mfspr(SPRN_PVR);
> > svid = mfspr(SPRN_SVR);
> >
> > - seq_printf(m, "Vendor\t\t: Freescale Semiconductor\n");
> > + seq_printf(m, "Vendor\t\t: %s\n",
Hi Vitaly,
When you will send out your 8xx/82xx series patches?
Thanks
Mark Zhan
On Tue, 2007-07-17 at 04:44 +0400, Vitaly Bordug wrote:
> On Mon, 16 Jul 2007 17:01:28 +0800
> Mark Zhan wrote:
>
> > These 3 patches add the powerpc support of Wind River SBC
> > PowerQUICCII.
> >
> I am sorry, bu
On Tue, Jul 17, 2007 at 12:16:27AM -0500, Kumar Gala wrote:
> Greg,
>
> Can you look at pulling these fixes for the next 2.6.22.x stable release.
Can you send them as patches, to the [EMAIL PROTECTED] address, after
they go into Linus's tree?
thanks,
greg k-h
_
Greg,
Can you look at pulling these fixes for the next 2.6.22.x stable
release.
- k
On Jul 17, 2007, at 12:07 AM, Jeff Garzik wrote:
> Andy Fleming wrote:
>> A few bugs in the Vitesse PHY driver were found on the 8641D HPCN
>> board.
>> Originally, they were masked by a bug in the PHY Lib w
Andy Fleming wrote:
> A few bugs in the Vitesse PHY driver were found on the 8641D HPCN board.
> Originally, they were masked by a bug in the PHY Lib which was fixed by patch
> 5f708dd91d15876e26d7a57f97a255cedffca463 (Fix phy_id for Vitesse 824x PHY).
> That patch allowed the Vitesse PHY to bind
Hello Arnd,
I think, the function of_find_compatible_node(), which is called in the
for loop, has already done that. So definitely, no need to call
of_device_is_compatible() any more.
Thanks
Mark Zhan
On Tue, 2007-07-17 at 03:02 +0200, Arnd Bergmann wrote:
> On Monday 16 July 2007, Mark Zhan wrot
> I still haven't seen much code using the feature or
> even any anecdotal information about the performance impact.
Here's some anecdotal evidence :)
http://lists.openfabrics.org/pipermail/general/2007-May/035758.html
--
MST
___
Linuxppc-dev mailing l
> > Why the module parameter? Is there any reason a user would want to
> > turn this off? Or conversely, why is it off by default?
>
> We're pretty confident this new feature works, but as with all new and
> possibly experimental features, there are chances it might explode your
> machin
> No, I've no figures to provide here. The background of this dist_eqs
> option is actually to allow us testing across all event queues
> without to change the testcases resp consumers to use certain
> event queue number. Thus, I should comment it as EXPERIMENTAL?
Seems like it's just developm
From: Roy Zang <[EMAIL PROTECTED]>
Change the pci express controller node name from pci
to pcie in device tree.
Signed-off-by: Roy Zang <[EMAIL PROTECTED]>
---
Based on Kumar tree and my previous patch for 8544DS
board.
arch/powerpc/boot/dts/mpc8544ds.dts|6 +++---
arch/powerpc/boot/dts
On Wed, Jul 11, 2007 at 02:03:24AM +0200, Segher Boessenkool wrote:
> >> Yeah. Giving the warning is a good thing though.
> >
> > No, it isn't; it's just noise, if we're not ever going to do anything
> > to prevent the behaviour - and we can't.
>
> The same userland code will not run correctly on
On Tue, Jul 17, 2007 at 07:47:26AM +1000, Benjamin Herrenschmidt wrote:
> > That "typical practice" is inspired by the need to explicitly
> > put #address-cells and #size-cells into the device tree if you
> > want Linux to properly parse the device tree, even if the default
> > values would work pe
> or maybe generate disconnect/connect events so udev rules can reconfigure
> each keyboard?
Possibly... That would be obtained by just removing/re-adding the
devices (CONFIG_HOTPLUG is necessary to get the infrastructure for that
afaik).
Ben.
___
Li
On Mon, 2007-07-16 at 23:00, Segher Boessenkool wrote:
> is this the only fix, I've already applied a version of this to
> my
> tree (with the irq sense fix) and just want to make sure there
> isn't
> anything else.
> >>> I do not get more.
> >>> I'd like to enroll Segher's su
Hi Benjamin,
> I don't think class device is the right approach. Classes are supposed
> to be a functional binding, ie, in this case, input devices. ADB is a
> bus, and as such, you should create an adb bus type and and adb_device
> that is an extension of struct device, not struct class device.
ok
On Monday 16 July 2007, Mark Zhan wrote:
> This patch addes the powerpc support to Wind River SBC PowerQUICCII 82xx
> board.
Hi Mark!
I've got lots of small comments about your code, but mostly it comes
down to one problem: your new platform code is not able to coexist
with other platforms becau
The Vitesse PHY on the 8641D needs to be set up with internal delay to
work in RGMII mode. So we add skew when it is set to RGMII_ID mode.
Signed-off-by: Andy Fleming <[EMAIL PROTECTED]>
Signed-off-by: Haruki Dai <[EMAIL PROTECTED]>
Signed-off-by: Haiying Wang <[EMAIL PROTECTED]>
---
drivers/net
The TSEC/eTSEC automatically detect their PHY interface type, unless
the type is RGMII-ID (RGMII with internal delay). In that situation,
it just detects RGMII. In order to fix this, we need to pass in rgmii-id
if that is the connection type.
Signed-off-by: Andy Fleming <[EMAIL PROTECTED]>
---
The Vitesse 824x PHY doesn't allow an interrupt to be cleared if
the mask bit for that interrupt isn't set. This means that the PHY
Lib's order of handling interrupts (disable, then clear) breaks on this
PHY. However, clearing then disabling the interrupt opens up the code
for a silly race condit
The TSEC/eTSEC can detect the interface to the PHY automatically,
but it isn't able to detect whether the RGMII connection needs internal
delay. So we need to detect that change in the device tree, propagate
it to the platform data, and then check it if we're in RGMII. This fixes
a bug on the 864
A few bugs in the Vitesse PHY driver were found on the 8641D HPCN board.
Originally, they were masked by a bug in the PHY Lib which was fixed by patch
5f708dd91d15876e26d7a57f97a255cedffca463 (Fix phy_id for Vitesse 824x PHY).
That patch allowed the Vitesse PHY to bind on the 8641D HPCN board, the
From: John Traill <[EMAIL PROTECTED]>
The 8xx can only support a max of 8M during early boot ( it seems a lot of
8xx boards only have 8M so the bug was never triggered ). The following
change makes it able to run with 128M.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/mm/
On Monday 16 July 2007, Mark Zhan wrote:
> - cpm_uart_data.uart_clk = ppc_proc_freq;
> + if (strstr(model, "SMC")) {
> + cpm_uart_dev =
> platform_device_register_simple("fsl-cpm-smc:uart",
> +
On Monday 16 July 2007, Mark Zhan wrote:
> @@ -96,7 +94,7 @@
> pvid = mfspr(SPRN_PVR);
> svid = mfspr(SPRN_SVR);
>
> - seq_printf(m, "Vendor\t\t: Freescale Semiconductor\n");
> + seq_printf(m, "Vendor\t\t: %s\n", CPUINFO_VENDOR);
> seq_printf(m, "Machine\t\t: %s\n", CPUI
This adds support for USB device mode on mpc831x series.
Devicetree node modification is required to make it work -
dr_mode ="peripheral";
which should be commented out if host mode is desired onboot.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_soc.c |1
Modifies fsl_ehci code so that to get USB host working on
mpc831x platform. Verified with MPC8313RDB reference board.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc8313erdb.dts |1 +
drivers/usb/host/ehci-fsl.c |4 +++-
drivers/usb/host/ehci-hc
This utilises pretend phy, making access to it via device tree. GiGE switch
is connected to TSEC1 with fixed gigE link, so we need to emulate it
via artificial PHY to make it work.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc8313erdb.dts |1 +
arch/pow
This enables DS1337 embedded RTC and uses "clock-frequency"
property to configure loops_per_jiffy. Fixed spaces vs tabs issue
in couple of places.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/83xx/mpc8313_rdb.c | 52 -
1 files change
On Mon, 16 Jul 2007 17:01:28 +0800
Mark Zhan wrote:
> These 3 patches add the powerpc support of Wind River SBC
> PowerQUICCII.
>
I am sorry, but this would intercept with big 8xx/82xx series from
Scott Wood I am reviewing now. it makes the initial merged code
more maintainable and powerpc-frien
device_bind_driver() error code returning has been fixed.
release() function has been written, so that to free resources
in correct way; the release path is now clean.
Before the rework, it used to cause
Device '[EMAIL PROTECTED]:1' does not have a release() function, it is broken
and mu
On Mon, 2007-07-16 at 16:53 -0400, Aristeu Rozanski wrote:
> This patch adds a class device for each adb device that has a handler.
> The class device contents will be accessible by /sys/class/adb/N
> directory. This patch is needed in order to add an class device
> attribute to all keyboards that
On Mon, 2007-07-16 at 16:53 -0400, Aristeu Rozanski wrote:
> When a Fn key is used in combination with another key in ADB keyboards
> it will generate a Fn event and then a second event that can be a
> different key than pressed (Fn + F1 for instance can generate Fn +
> brightness down if it's conf
On Mon, 2007-07-16 at 17:18 -0500, Scott Wood wrote:
>
> OK... but if you're doing a pure IRQ number conversion, the only useful
> #address-cells would be zero, which makes it a reasonable default IMHO
> (unlike the arbitrary 2 for regular traversal).
It does make a reasonable default. The thi
Alexandre Bounine wrote:
> From: Alexandre Bounine <[EMAIL PROTECTED]>
>
> This patch improves performance of the Tsi108 Ethernet driver by
> changing interrupt handling for frame receive path. It reduces number of
> interrupts generated for received frames and therefore lowers CPU
> utilization b
Benjamin Herrenschmidt wrote:
> No, interrupt maps are useful in devices with no children in some corner
> cases. Remember that a map doesnt need to use the address part of the
> source specifier, thus it can be used to do a pure domain->domain
> conversion of the irq numbers, what sort of thing. T
On Mon, 2007-07-16 at 17:03 -0500, James Bottomley wrote:
> On Tue, 2007-07-17 at 07:49 +1000, Benjamin Herrenschmidt wrote:
> > > No ... that was the point of flush_kernel_dcache_page(). The page in
> > > question is page cache backed and contains user mappings. However, the
> > > block layer ha
> > I would personally be inclined to define that whatever spec we come up
> > with always require #address-cells/#size-cells for any node that can
> > have either device children or interrupt children, and ban default
> > values alltogether.
>
> Did you really mean #size-cells here? Shouldn't i
On Mon, 2007-07-16 at 16:55 -0500, Scott Wood wrote:
> Benjamin Herrenschmidt wrote:
> > I would personally be inclined to define that whatever spec we come up
> > with always require #address-cells/#size-cells for any node that can
> > have either device children or interrupt children, and ban def
On Tue, 2007-07-17 at 07:49 +1000, Benjamin Herrenschmidt wrote:
> > No ... that was the point of flush_kernel_dcache_page(). The page in
> > question is page cache backed and contains user mappings. However, the
> > block layer has already done a flush_dcache_page() in get_user_pages()
> > and t
Thomas Klein wrote:
> This patch adds support for DLPAR memory add to the eHEA driver. To detect
> whether memory was added the driver uses its own memory mapping table and
> checks for kernel addresses whether they're located in already known memory
> sections. If not the function ehea_rereg_mrs()
From: [EMAIL PROTECTED] (Linas Vepstas)
Date: Mon, 16 Jul 2007 12:25:35 -0500
> On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote:
> > From: [EMAIL PROTECTED] (Linas Vepstas)
> > Date: Fri, 13 Jul 2007 15:05:15 -0500
> >
> > >
> > > This is a patch (& bug report) for a crash in sysctl
[snip]
> There is no child device node, but there are child interrupt
> nodes, and
> since the interrupt-tree uses #address/size-cells, it does make some
> sense to specify them.
>
> Yes, there is a default value when absent, but the simple
> fact that the
> default is different depending if yo
Benjamin Herrenschmidt wrote:
> I would personally be inclined to define that whatever spec we come up
> with always require #address-cells/#size-cells for any node that can
> have either device children or interrupt children, and ban default
> values alltogether.
When is #size-cells used in the i
On Mon, 2007-07-16 at 18:35 +0200, Geert Uytterhoeven wrote:
> The config symbol for SPE support is called CONFIG_SPU_BASE, not
> CONFIG_SPE_BASE.
Oops... Arnd, we need to check the distro kernels here.
> Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
Acked-by: Benjamin Herrenschmidt <[EM
> No ... that was the point of flush_kernel_dcache_page(). The page in
> question is page cache backed and contains user mappings. However, the
> block layer has already done a flush_dcache_page() in get_user_pages()
> and the user shouldn't be touching memory under I/O (unless they want
> self
On Mon, 2007-07-16 at 16:34 +0200, Segher Boessenkool wrote:
> >>> + #address-cells = <0>;
> >>> + #size-cells = <0>;
> >>
> >> No need for these.
> >
> > Isn't a good practice to put #address-cells in interrupt controller
> > nodes?
>
> It is not.
Well, that's debatable... but ye
On Mon, 2007-07-16 at 08:47 -0500, James Bottomley wrote:
>
> No ... that was the point of flush_kernel_dcache_page(). The page in
> question is page cache backed and contains user mappings. However,
> the
> block layer has already done a flush_dcache_page() in get_user_pages()
> and the user sh
> Upon closer look, while flush_kernel_dcache_page() is a no-op on ppc64,
> flush_dcache_page() isn't. So I'd prefer to not call it if not really needed.
>
> And according to James, flush_kernel_dcache_page() should be sufficient...
>
> So I'm getting puzzled again...
flush_dcache_page() handle
On Mon, 2007-07-16 at 09:59 +0100, Matt Sealey wrote:
> You could do a LOT worse than check the Pegasos.
Yes, mimmicing the pegasos will probably work
> Matt Sealey <[EMAIL PROTECTED]>
> Genesi, Manager, Developer Relations
>
> Gerhard Pircher wrote:
> > Hi,
> >
> > I wonder, if there is a reco
Hi
Just noticed, that of_flat_dt_is_compatible() is only ever used with node
= of_get_flat_dt_root(). So, unless we ever plan to use it otherwise,
someone might want to simplify it a bit:-)
Thanks
Guennadi
---
Guennadi Liakhovetski
___
Linuxppc-dev ma
Roland Dreier <[EMAIL PROTECTED]> wrote on 16.07.2007 19:37:09:
> > If enabled via the mr_largepage module parameter,
>
> Why the module parameter? Is there any reason a user would want to
> turn this off? Or conversely, why is it off by default?
We're pretty confident this new feature works
This patch adds an sysfs attribute to each handled ADB keyboard in order
to support runtime sysrq key configuration. This is needed because some
machines don't have the default sysrq key (0x69). The key will be
configurable by /sys/class/adb/keyboard/sysrq_key.
Signed-of-by: Aristeu Rozanski <[EMA
This patch adds a class device for each adb device that has a handler.
The class device contents will be accessible by /sys/class/adb/N
directory. This patch is needed in order to add an class device
attribute to all keyboards that will determine the sysrq key for each
keyboard.
Signed-of-by: Aris
These two patches make possible to configure the sysrq key on ADB based
machines where the default sysrq key (0x69) is not present. The first
patch creates a class device for each handled device. The second one adds an
attribute to ADB keyboards that makes possible to configure the sysrq key
for ea
When a Fn key is used in combination with another key in ADB keyboards
it will generate a Fn event and then a second event that can be a
different key than pressed (Fn + F1 for instance can generate Fn +
brightness down if it's configured like that). This patch enables the
reporting of the Fn key t
Hi,
this bug exists since I began using a powerbook 12". When the
system gets hot, therm_adt746x begins to oscillate between two fan
speeds every one or two seconds. The result is very annoying not
optimal: while switching between two speeds, the machine takes a long
time to get cold again.
Roland Dreier <[EMAIL PROTECTED]> wrote on 16.07.2007 18:04:26:
> Do you have any data on how well this round-robin assignment works?
> It seems not quite right to me for the driver to advertise nr_eqs
> completion vectors, but then if round-robin is turned on to ignore the
> consumer's decision ab
Roland Dreier <[EMAIL PROTECTED]> wrote on 16.07.2007 19:14:03:
> applied, but as a further cleanup it seems that ehca2ib_return_code()
> should be moved into a .c file and moved out of line -- I think it
> would probably shrink the compiled code quite a bit, and as far as I
> can see it is never
Roland Dreier <[EMAIL PROTECTED]> wrote on 16.07.2007 18:04:26:
> It seems not quite right to me for the driver to advertise nr_eqs
> completion vectors, but then if round-robin is turned on to ignore the
> consumer's decision about which vector to use.
The round-robin feature was primarily meant
This patch addes the powerpc support to Wind River SBC PowerQUICCII 82xx board.
Signed-off-by: Mark Zhan <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/sbcpq2.dts | 191 +++
arch/powerpc/configs/sbcpq2_defconfig | 917
++
arch/powerpc/platforms/82xx/K
Some mpc82xx platform hooks in mpc82xx_ads.c are actually not specific to ads
board, they could be shared by different
82xx boards.
Signed-off-by: Mark Zhan <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/82xx/mpc82xx.c | 30 +++
arch/powerpc/platforms/82xx/mpc82xx_ad
This patch makes 'cpm_uart_of_init' be able to parses SMC serial device node in
DTS
Signed-off-by: Mark Zhan <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_soc.c | 37 -
1 file changed, 20 insertions(+), 17 deletions(-)
Index: linux-powerpc-2.6.x/arch/po
Hi,
still working on mapping a Mach-O driver to ELF, I'm seeing a weird
kOops when insmod'ing the driver :
Jul 16 20:16:07 tertius kernel: Oops: Unrecoverable FP Unavailable Exception,
sig: 6 [#1]
Jul 16 20:16:07 tertius kernel: PREEMPT
Jul 16 20:16:07 tertius kernel: Modules linked in: unicorn
> Update mpc7448hpc2 device tree to be compatible for tsi109 chip.
>
> Signed-off-by: Roy Zang <[EMAIL PROTECTED]>
Looks good, thanks!
Segher
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
These 3 patches add the powerpc support of Wind River SBC PowerQUICCII.
1) Currently, some mpc82xx platform hooks in mpc82xx_ads.c are actually not
specific to ads board. So the 1st patch
makes them be shared by different 82xx boards.
2) The 2nd patch make 'cpm_uart_of_init' be able to parse SM
> Add support for MR pages larger than 4K on eHCA2. This reduces firmware
> memory consumption. If enabled via the mr_largepage module parameter, the MR
> page size will be determined based on the MR length and the hardware
> capabilities - if the MR is >= 16M, 16M pages are used, for example.
From: Alexandre Bounine <[EMAIL PROTECTED]>
This patch improves performance of the Tsi108 Ethernet driver by
changing interrupt handling for frame receive path. It reduces number of
interrupts generated for received frames and therefore lowers CPU
utilization by the device driver.
Signed-off-b
On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote:
> From: [EMAIL PROTECTED] (Linas Vepstas)
> Date: Fri, 13 Jul 2007 15:05:15 -0500
>
> >
> > This is a patch (& bug report) for a crash in sysctl_set_parent()
> > in 2.6.22-git2.
> >
> > Problem: 2.6.22-git2 crashes with a stack trac
I agree that 20 ms is not the best option. But, as you mentioned as
well, shorter period may bring more wasted CPU cycles.
Using this approach to interrupt moderation I see performance
improvement using frame flow that generates about one interrupt per
frame. Below are CPU usage numbers reported by
On Fri, Jul 13, 2007 at 07:06:56PM -0600, Eric W. Biederman wrote:
> > .data = &ipv4_devconf.loop,
> > .maxlen = sizeof(int),
> > .mode = 0644,
> > + .child = 0x0,
> > .pro
> @@ -161,8 +161,11 @@ static inline int ehca2ib_return_code(u64 ehca_rc)
applied, but as a further cleanup it seems that ehca2ib_return_code()
should be moved into a .c file and moved out of line -- I think it
would probably shrink the compiled code quite a bit, and as far as I
can see it is nev
It looks real good now :-)
One tiny comment...
> + [EMAIL PROTECTED] {
> + compatible = "fsl,mpc8548-pcie";
I would name the node [EMAIL PROTECTED] instead; generic names
aren't for machine consumption anyway, and most humans
want to know which buses are plain PCI
On Monday 16 July 2007, Geert Uytterhoeven wrote:
> On Sat, 14 Jul 2007, Mike Frysinger wrote:
> > Pretty much everyone uses "__attribute__" or "attribute", no one
> > uses "__attribute". This patch tweaks the three places in asm-powerpc
> > where this comes up. While only asm-powerpc/types.h is
>> Well, they aren't supposed to :-) The problem at this point is
>> more due
>> to the fact that for things that haven't been specified by
>> official OF
>> bindings, people are going all over trying to define their own and
>> sometimes conflicting bindings and then changing them.
>
> I think
The config symbol for SPE support is called CONFIG_SPU_BASE, not
CONFIG_SPE_BASE.
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
diff --git a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c
index 4f2f453..0b25d42 100644
--- a/arch/powerpc/mm/hash_utils_64.c
+++ b/arch/pow
> As I wrote a couple of times already, it's a perfectly acceptable
> approach to have "constructors" (what you call oftree-interpreter)
> that
> generate platform devices from the OF tree.
Yes, lots of the "glue" code could be made into some
helper library. Also, while that glue code might be
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a BD/DVD/CD-ROM Storage Driver for the PS3:
- Implemented as a SCSI device driver
- Uses software scatter-gather with a 64 KiB bounce buffer as the hypervisor
doesn't support scatter-gather
CC: Geoff Levand <[EMAIL PROTECTED]>
Signed-off-by
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a FLASH ROM Storage Driver for the PS3:
- Implemented as a misc character device driver
- Uses a fixed 256 KiB buffer allocated from boot memory as the hypervisor
requires the writing of aligned 256 KiB blocks
CC: Geoff Levand <[EMAIL PROTE
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Add a Disk Storage Driver for the PS3:
- Implemented as a block device driver with a dynamic major
- Disk names (and partitions) are of the format ps3d%c(%u)
- Uses software scatter-gather with a 64 KiB bounce buffer as the hypervisor
doesn't
Hi,
These are the remaining patches of the new PS3 storage drivers series:
[1] ps3: Disk Storage Driver
[2] ps3: BD/DVD/CD-ROM Storage Driver
[3] ps3: FLASH ROM Storage Driver
They are based on:
- the current Linux kernel source tree,
- plus the PS3 patches already submitted by
> Is there a reason why there is sooo much interaction of the
> platform code with the oftree?
Yes. Since the decision has been made to require a device
tree for every platform, arch/powerpc is in the luxury
position that we can actually exploit the benefits of _having_
a tree for every platform.
>> Hmm, as I stated above: Handling the SPI slave devices is done in
>> the SPI
>> framework. But including this data into the dts sounds better than
>> including
>> it into the BSP. Is there some documentation around how to
>> describe such a
>> SPI bus with its devices in the dts?
>
> I don
> The eHCA driver can now handle multiple event queues (read: interrupt
> sources) instead of one. The number of available EQs is selected via the
> nr_eqs module parameter.
> CQs are either assigned to the EQs based on the comp_vector index or, if the
> dist_eqs module parameter is supplied,
On Fri, 2007-07-13 at 19:05 +0200, Olaf Hering wrote:
> 2.6.21 arch/powerpc/configs/iseries_defconfig works on an i825 with v5r4
> 2.6.22 arch/powerpc/configs/iseries_defconfig does not. But it works on
> a i820 with v5r3.
> 2.6.22 boots ok with CONFIG_VIOCONS
When it works, do you have more than
>>> I wonder, if there is a recommended way to specify ISA register
>>> addresses and interrupts for a PCI device (unlike for a PCI2ISA
>>> bridge)?
>>
>> The PCI binding describes the required way to do this.
> Hmm, I must reread the PCI binding spec. It didn't seem to contain any
> information ab
is this the only fix, I've already applied a version of this to my
tree (with the irq sense fix) and just want to make sure there
isn't
anything else.
>>> I do not get more.
>>> I'd like to enroll Segher's suggestion together with VIA chip
>>> function
>>> in next step.
>>>
On Mon, 16 Jul 2007, Jens Axboe wrote:
> On Mon, Jul 16 2007, James Bottomley wrote:
> > On Mon, 2007-07-16 at 14:16 +0200, Jens Axboe wrote:
> > > On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> > > > On Fri, 13 Jul 2007, Geert Uytterhoeven wrote:
> > > > > Ah, that explains it. flush_dcache_page
> It's not that bad in most respects, though unlike some, I don't
> think we need to stick dogmatically to the exact way that Open
> Firmware(tm) did everything.
s/did/does/
And for the record: neither do I.
Segher
___
Linuxppc-dev mailing list
L
> I thought the idea of the dts/of was for the hardware specific boot
> loader to tell the kernel about hardware that the kernel couldn't
> otherwise know about, because its not detectable by a bus probe
> method,
> etc. Its not there to tell you how to use the device or arbitrate
> which
> oth
On Mon, Jul 16 2007, James Bottomley wrote:
> On Mon, 2007-07-16 at 14:16 +0200, Jens Axboe wrote:
> > On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> > > On Fri, 13 Jul 2007, Geert Uytterhoeven wrote:
> > > > Ah, that explains it. flush_dcache_page() is used in some drivers.
> > > > I'll update m
>>> + #address-cells = <0>;
>>> + #size-cells = <0>;
>>
>> No need for these.
>
> Isn't a good practice to put #address-cells in interrupt controller
> nodes?
It is not.
> If the device tree has an interrupt map defined the interrupt
> parent 'unit interrupt specifier' has to
On Jul 16, 2007, at 8:05 AM, Segher Boessenkool wrote:
>>> is this the only fix, I've already applied a version of this to my
>>> tree (with the irq sense fix) and just want to make sure there isn't
>>> anything else.
>> I do not get more.
>> I'd like to enroll Segher's suggestion together with V
On Mon, 2007-07-16 at 14:16 +0200, Jens Axboe wrote:
> On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> > On Fri, 13 Jul 2007, Geert Uytterhoeven wrote:
> > > Ah, that explains it. flush_dcache_page() is used in some drivers.
> > > I'll update my patches. Thanks for the comments!
> >
> > Does this
On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> On Mon, 16 Jul 2007, Geert Uytterhoeven wrote:
> > On Mon, 16 Jul 2007, Jens Axboe wrote:
> > > On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> > > > On Fri, 13 Jul 2007, Geert Uytterhoeven wrote:
> > > > > Ah, that explains it. flush_dcache_page()
Original-Nachricht
Datum: Mon, 16 Jul 2007 14:40:48 +0200
Von: Segher Boessenkool <[EMAIL PROTECTED]>
An: Gerhard Pircher <[EMAIL PROTECTED]>
CC: linuxppc-dev@ozlabs.org
Betreff: Re: Legacy ISA registers/interrupts in PCI device tree node
> > I wonder, if there is a recommended
On Mon, 16 Jul 2007, Geert Uytterhoeven wrote:
> On Mon, 16 Jul 2007, Jens Axboe wrote:
> > On Mon, Jul 16 2007, Geert Uytterhoeven wrote:
> > > On Fri, 13 Jul 2007, Geert Uytterhoeven wrote:
> > > > Ah, that explains it. flush_dcache_page() is used in some drivers.
> > > > I'll update my patches.
1 - 100 of 122 matches
Mail list logo
