On Saturday 06 October 2007, Benjamin Herrenschmidt wrote:
> On Sun, 2007-10-07 at 00:47 +0400, Peter Lemenkov wrote:
> > Hello All!
> > I can't compile one small software title because of lack
> > and inb/outb macros. What sould I do to overcome this obstacle?
> >
> > My linux distro is Fedora 7
Updates for PS3 os-area rtc_diff set/get routines
o Add a new routine ps3_os_area_set_rtc_diff().
o Rename ps3_os_area_rtc_diff() to ps3_os_area_get_rtc_diff().
o Remove static variable rtc_shift with calls to ps3_os_area_get_rtc_diff().
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
arch/po
Add support for a simple tagged database in the PS3 flash rom
os-area. The database allows the flash rom os-area to be shared
between a bootloder and installed operating systems. The
application ps3-flash-util or the library libps3-utils from the
ps3-utils package can be used for userspace datab
Add a workqueue to the PS3 os-area support. This is needed to
support writing updates to flash memory and to update the /proc
device tree entries from the timer tick interrupt context.
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/ps3/os-area.c | 23 +++
Updates for PS3 os-area startup params
o Remove some unused PS3 os-area startup params from struct saved_params.
o Rename ps3_os_area_init() to ps3_os_area_save_params().
o Zero mirrored header after saving params.
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/ps3/os-
Paul,
This is a small set of patches that reworks and improves
the 'other os' area of the PS3's flash rom.
Please apply for 2.6.24.
-Geoff
--
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Add the PS3 os-area startup params to the device tree. This allows
a second stage kernel loaded with kexec to use these values.
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/ps3/os-area.c | 104 +-
arch/powerpc/platforms/ps3/platform
Minor cleanup of the PS3 file os-area.c:
o Correct file text header.
o Add type names enum os_area_ldr_format, enum os_area_boot_flag,
enum os_area_ctrl_button.
o Change struct os_area_header.magic_num type to u8.
o Add preprocessor macro SECONDS_FROM_1970_TO_2000.
Signed-off-by: Geoff Leva
On Sun, 2007-10-07 at 00:47 +0400, Peter Lemenkov wrote:
> Hello All!
> I can't compile one small software title because of lack
> and inb/outb macros. What sould I do to overcome this obstacle?
>
> My linux distro is Fedora 7 if it is matter.
They don't exist in user space on non-x86. You have
Hello All!
I can't compile one small software title because of lack
and inb/outb macros. What sould I do to overcome this obstacle?
My linux distro is Fedora 7 if it is matter.
--
With best regards!
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.or
> "Kumar" == Kumar Gala <[EMAIL PROTECTED]> writes:
Kumar> On Oct 3, 2007, at 11:01 PM, Stephen Rothwell wrote:
>> On Wed, 03 Oct 2007 17:43:50 +0200 Peter Korsgaard
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> @@ -1220,14 +1220,17 @@ int __init fsl_spi_init(struct
>>> spi_board_info *board_i
On Oct 6, 2007, at 6:36 AM, Kumar Gala wrote:
> In a discussion with Hollis over beer he raised the question why
> TASK_SIZE is 0x8000 on ppc32.
Left over from the old days (2.1) of the PReP port when
things were hard coded. We used some of the space
between 0x8000 and 0xc000 for ma
In a discussion with Hollis over beer he raised the question why
TASK_SIZE is 0x8000 on ppc32.
I was wondering if anyone know why this was still the case? Seems
like we have a 1Gb whole between TASK_SIZE & KERNELBASE.
- k
___
Linuxppc-dev maili
Hello,
The following series of patches adds arch/powerpc support for three MPC5200
based boards:
TQM5200, CM5200 and Motion-PRO.
Included are also patches with modifications to common 52xx code. New helper
routine mpc52xx_find_and_map_path() is added, and is being used in LED driver
for Motion-P
The PCI device table in the powermac IDE driver isn't properly
terminated. Depending on how your kernel is linked and other random
factors, you can end up with this driver matched against any other PCI
device in your system, possibly crashing at boot.
Thanks to Heikki for tracking this down with m
15 matches
Mail list logo