t's pretty simple stuff
except also requires changes in the simpleboot wrapper. We will post them
shortly since they are relevant to this discussion.
John
--
John Williams, PhD, B. Eng, B. IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f
Hi Grant,
On Fri, Oct 8, 2010 at 4:34 AM, Grant Likely wrote:
> Reaching way back into the past
Indeed
> John, did you ever solve your issue here? Comments below.
The fix in our case was to explicitly add child nodes to the PCI
controller, with interrupt-parent and interrupts properties.
On Thu, May 27, 2010 at 3:29 AM, John Linn wrote:
> The code is not checking the interrupt for DMA correctly so that an
> interrupt number of 0 will cause a false error.
>
> Signed-off-by: Brian Hill
> Signed-off-by: John Linn
> ---
> drivers/net/ll_temac_main.c | 2 +-
> 1 files changed, 1
I looked at the ML510 DTS in boot/dts and
it's not doing anything like this.
As a footnote, I'm actually doing this in MicroBlaze whose PCI
infrastructure is not yet in mainline, however we copied this bit of
code directly from PPC and the logic is the
> + return rc;
Can this be better expressed like this:
my_func() {
mutex_lock()
..
if(some error) {
rc=-ETIMEDOUT;
goto out_unlock;
}
...
/* success path */
rc=0;
..
out_unlock:
mutex_unlock()
return rc;
}
Is this style still favoured in driver exit pa
Hi Wolfgang,
On Tue, Feb 9, 2010 at 8:48 AM, Wolfgang Denk wrote:
>> I'm looking at the simpleImage.XXX make target (PPC 405/440), and it
>> seems that by default the arch/powerpc/boot/wrapper script places the
>> bootwrapper at 0x40, effectively setting a limit on the maximum
>> bootable ker
Hi,
I'm looking at the simpleImage.XXX make target (PPC 405/440), and it
seems that by default the arch/powerpc/boot/wrapper script places the
bootwrapper at 0x40, effectively setting a limit on the maximum
bootable kernel size.
For various reasons we'd like to be able to put a fairly complet
er anyone tries to encode
anything non-hardware related into the DTS itself.
I guess I'd like to just open up a discussion, see if there's been any
progress towards a general solution.
Thanks,
John
--
John Williams
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalog
$(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
where vmlinux is a dependency of the whole simpleImage/DTB binding process.
Anyway input on both the approach, and how to achieve it, would be
greatly appreciated before we go working to deeply on the
implementation.
Thank
On Tue, Apr 21, 2009 at 12:48 AM, Grant Likely
wrote:
> On Mon, Apr 20, 2009 at 8:36 AM, John Linn wrote:
>>> -Original Message-
>>> From: Stephen Neuendorffer
>>> Sent: Sunday, April 19, 2009 11:52 PM
>>> To: John Williams; microblaze-u
sn't we
have to fix it), but there'll be no platform_device_register() call in
their machine startup to actually cause driver / device binding.
No harm, no foul. Problem goes away.
Then, as Grant points out, the rare cases where non-Xilinx platforms
do use this stuff, they'll presumably k
Hi Steve,
> In my opionion, we should only include dts files for reference designs, and
> it must be documented how to get the design that the dts corresponds to.
I'm not sure you (or Xilinx) are quite ready for the pain this implies
- have you tried browsing reference designs on Xilinx.com recen
On Sat, Jun 28, 2008 at 3:49 PM, Grant Likely <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 26, 2008 at 5:29 AM, <[EMAIL PROTECTED]> wrote:
>> From: Michal Simek <[EMAIL PROTECTED]>
>> arch/microblaze/platform/generic/system.dts | 300
>> +++
> Since this is a generated file
that will
also include the glibc tools.
Cheers,
John
--
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.
le that we drop into
the kernel build. Doing so ensures consistency between the hardware
and the kernel running on it.
These options come out of the tools as intergers, 0,1,2. We found in
the early days of microblaze that lots of users built unbootable
kernels because they manually transcribed the
15 matches
Mail list logo
