On 2020-03-25 10:37:57 [+0200], Felipe Balbi wrote:
> Do you want to carry it via your tree? If so:
We would like to do so.
> Acked-by: Felipe Balbi
Thank you.
> Otherwise, let me know and I'll pick this patch.
Sebastian
On 2020-03-25 09:39:19 [-0700], Paul E. McKenney wrote:
> > > --- a/Documentation/locking/locktypes.rst
> > > +++ b/Documentation/locking/locktypes.rst
> > …
> > > +rw_semaphore
> > > +
> > > +
> > > +rw_semaphore is a multiple readers and single writer lock mechanism.
> > > +
> > > +On
On 2020-03-25 13:27:49 [+0100], Thomas Gleixner wrote:
> The documentation of rw_semaphores is wrong as it claims that the non-owner
> reader release is not supported by RT. That's just history biased memory
> distortion.
>
> Split the 'Owner semantics' section up and add separate sections for
> s
The warning was intended to spot complete_all() users from hardirq
context on PREEMPT_RT. The warning as-is will also trigger in interrupt
handlers, which are threaded on PREEMPT_RT, which was not intended.
Use lockdep_assert_RT_in_threaded_ctx() which triggers in non-preemptive
context on PREEMPT
Kumar Gala wrote:
are you trying to get this accepted?
If the reviewer don't have any objections yes. You sound
like there is something terrible wrong. Do you want it in smaller pieces?
- k
Sebastian
--
Firmensitz: 88690 Uhldingen, Auf dem Berg 3
Registergericht: Amtsgericht Freiburg i. Br.
Milton Miller wrote:
|load: entry = 0x80053c flags = 0
|nr_segments = 2
|segment[0].buf = 0x1002b8f0
|segment[0].bufsz = 80
|segment[0].mem = (nil)
|segment[0].memsz = 1000
|segment[1].buf = 0x4803f008
|segment[1].bufsz = 3a3138
|segment[1].mem = 0x80
|segment[1].memsz = 3b
I w
* Milton Miller | 2008-09-23 20:24:02 [-0500]:
>If you have any questions about kdump or what needs to happen,
>please feel free to contact me either by email or on irc (sometimes
>I use mdm other times the email login as my nick, and when connected
>I tend to leave it well past the hours I am at
* Milton Miller | 2008-09-23 20:46:18 [-0500]:
>On Wed Sep 24 at about 06:38:57 EST in 2008, Sebastian Siewior wrote:
>> My mylinux binary incl. bss is ~5 MiB without bss less than 4 MiB.
>> Therefore I though that I could replace ei.memsize with ei.loadsize. It
>> didn
Milton Miller wrote:
My current (working) solution is to move cuImage from 4 MiB to 8 MiB.
Something similar has been done for pSeries in 9b09c6d "powerpc: Change
the default link address for pSeries zImage kernels". Would it be
appropriate to move initial address to 64 MiB as the default loading
Milton Miller wrote:
On Wed Sep 24 at about 05:54:04 EST 2008, Sebastian Siewior wrote:
this could be used by the kexec userland code.
NACK.
[...]
Thanks for explanation. I just went through the kexec user land code and
saw that the 64bit code uses the device tree to obtain some address and
Kumar Gala wrote:
I missing why you are doing this? Do you plan on using it w/32-bit kexec?
Yes. I plan to kexec my mpc8544 board.
- k
Sebastian
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-de
My mylinux binary incl. bss is ~5 MiB without bss less than 4 MiB.
Therefore I though that I could replace ei.memsize with ei.loadsize. It
didn't work. I'm not sure why it did not work but I guess that the
memset() of bss in the initial kernel code overwrote the cuimage code
which is required for s
this could be used by the kexec userland code.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
This is done by the 64bit kexec code allready. The 32bit doesn't use the
device tree at all. I'm not sure whether the node has to be a 32bit or
64bit value.
arch/powerpc/bo
* David Gibson | 2008-08-25 19:36:17 [+1000]:
>Make sure the device tree contains a linux,stdout-path property in
>/chosen.
Oh. it did the trick.
Thanks.
Sebastian
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinf
From: Thiemo Seufer <[EMAIL PROTECTED]>
those two are requried on my fresh gcc 4.3.1
Signed-off-by: Thiemo Seufer <[EMAIL PROTECTED]>
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
Not sure if this is intendent or a gcc bug but with -mno-spe
the spe opcodes were not u
* Arnd Bergmann | 2008-08-21 00:40:58 [+0200]:
>On Wednesday 20 August 2008, Sebastian Siewior wrote:
>> I didn't convert the NDFC driver to support OF because there are
>> non-OF-aware platforms with the ndfc chip.
>> All settings are mandatory except the oob layout.
I have here a mpc8540ads board and a u-boot 1.0.0. I've build the
defconfig for the board and I tried to boot the genarated
cuImage.mpc8540ads image. After the bootm command I see just
|8540> bootm 100
|## Booting image at 0100 ...
| Image Name: Linux-2.6.26
| Image Type: PowerPC L
I didn't convert the NDFC driver to support OF because there are
non-OF-aware platforms with the ndfc chip.
All settings are mandatory except the oob layout.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
drivers/mtd/nand/Kconfig |7 ++
drivers/mtd/nand/Makef
* Benjamin Herrenschmidt | 2008-08-14 13:45:54 [+1000]:
>> The fix is to defer phy init until netdevice is registered / initialized.
>
>I think it's better instead to take the dev_mc_add() statement
>out of emac_configure().
I looked yesterday into that code and I saw that dev_mc_add() was called
+0x44/0x60
The fix is to defer phy init until netdevice is registered / initialized.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
Noticed with spinlock debug enabled & 40x/kilauea_defconfig on a kilaue
board. With this patch, the board boots via NFS root, no problems were
* Benjamin Herrenschmidt | 2008-07-24 08:12:48 [+1000]:
>On Mon, 2008-07-21 at 17:57 -0500, Nate Case wrote:
>> On Fri, 2008-07-18 at 14:10 +0200, Sebastian Siewior wrote:
>> > Commit 35b5f6b1a aka [PHYLIB: Locking fixes for PHY I/O potentially
>> > sleeping]
>>
From: Sebastian Siewior <[EMAIL PROTECTED]>
I got the following backtrace while network was unavailble:
|NETDEV WATCHDOG: eth0: transmit timed out
|BUG: sleeping function called from invalid context at
/home/bigeasy/git/linux-2.6-powerpc/kernel/mutex.c:87
|in_atomic():1, irqs_disabled():0
* Nate Case | 2008-07-21 17:57:08 [-0500]:
>On Fri, 2008-07-18 at 14:10 +0200, Sebastian Siewior wrote:
>> Commit 35b5f6b1a aka [PHYLIB: Locking fixes for PHY I/O potentially sleeping]
>> changed the phydev->lock from spinlock into a mutex. Now, the following
>> code path
Commit 35b5f6b1a aka [PHYLIB: Locking fixes for PHY I/O potentially sleeping]
changed the phydev->lock from spinlock into a mutex. Now, the following
code path got triggered while NFS was unavailable:
|[ 21.287359] nfs: server 10.11.3.47 not responding, still trying
|[ 38.891373] nfs: server 1
* Olof Johansson | 2008-06-25 16:22:50 [-0500]:
>> Kumar / Josh: Should we describe those DT entries in
>> Documentation/powerpc/booting-without-of.txt? In the yes case: which
>> section do you recommend?
>
>I don't see a need to. We don't document the IBM busses there either.
Okey.
>
>
>-Olof
OF device tree. The PCI
>interface still assumes the same default values.
>
>Signed-off-by: Nate Case <[EMAIL PROTECTED]>
Acked-by: Sebastian Siewior <[EMAIL PROTECTED]>
>diff --git a/drivers/usb/host/isp1760-if.c b/drivers/usb/host/isp1760-if.c
>index 440bf94..56e2ad6 100
* Nate Case | 2008-05-21 16:28:51 [-0500]:
>This adds support for hardware configurations that don't match the
>chip default register settings (e.g., 16-bit data bus, DACK and
>DREQ pulled down instead of up, analog overcurrent mode).
Nice patch. A few comments inline.
>These settings are passed
dering why it was correct in other places like
/proc/iomem :)
Acked-by: Sebastian Siewior <[EMAIL PROTECTED]>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
This patch contains the entry for the build system and glue code for the
platform bus. Currently OpenFirmware and PCI is supported.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
--- a/drivers/usb/host/Kconfig
+++ b/drivers/usb/host/Kconfig
@@ -95,6 +95,32 @@ config USB_ISP11
* Geert Uytterhoeven | 2007-07-12 10:40:47 [+0200]:
>If you're using a PS3 with a HDMI or DVI-D(+HDCP) monitor, please give it a
>try.
Got 1920x1200 @60Hz on my Eizo FlexScan S2411W on boot. No quirk
required for that one :)
>(BTW, even if autodetect works fine, I always welcome this information)
30 matches
Mail list logo
