From: Frank Neuber <frank.neuber@kernelport.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Florian Fainelli <florian@openwrt.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: AU1550 Kernel bug detected[#1] clockevents_register_device
Date: Wed, 28 Jan 2009 11:38:25 +0100 [thread overview]
Message-ID: <1233139105.28527.547.camel@t60p> (raw)
In-Reply-To: <20090128094552.GA25480@roarinelk.homelinux.net>
Am Mittwoch, den 28.01.2009, 10:45 +0100 schrieb Manuel Lauss:
> > > --- a/include/asm-mips/mach-au1x00/au1000.h
> > > +++ b/include/asm-mips/mach-au1x00/au1000.h
> > > @@ -1679,12 +1679,21 @@ enum soc_au1200_ints {
> > > #define Au1500_PCI_MEM_START 0x440000000ULL
> > > #define Au1500_PCI_MEM_END 0x44FFFFFFFULL
> > >
> > > +#if 1
> > > +#define PCI_IO_START 0x00001000
> > > +#define PCI_IO_END 0x000FFFFF
> > > +#define PCI_MEM_START 0x40000000
> > > +#define PCI_MEM_END 0x4FFFFFFF
> > > +#define PCI_FIRST_DEVFN (0 << 3)
> > > +#define PCI_LAST_DEVFN (19 << 3)
>
> The current -git sources already have this change. How come yours
> don't? (it was changed before 2.6.24).
Because I try to track down the PCI resource management problem in
2.6.24 I want to test older versions which does not have this problem
(like 2.6.16) or now after enabeling CONFIG_64BIT_PHYS_ADDR 2.6.19.
For next I will look at 2.6.23 what the problem is with the recource
conflict ....
Regards,
Frank
next prev parent reply other threads:[~2009-01-28 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 8:44 AU1550 Kernel bug detected[#1] clockevents_register_device Frank Neuber
2009-01-27 9:11 ` Manuel Lauss
2009-01-27 9:18 ` Florian Fainelli
2009-01-27 9:23 ` Florian Fainelli
2009-01-27 10:13 ` Frank Neuber
2009-01-27 12:11 ` Manuel Lauss
2009-01-27 12:42 ` Frank Neuber
2009-01-28 9:19 ` Frank Neuber
2009-01-28 9:38 ` Manuel Lauss
2009-01-28 9:45 ` Manuel Lauss
2009-01-28 10:38 ` Frank Neuber [this message]
2009-01-28 10:31 ` Frank Neuber
2009-01-29 21:35 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233139105.28527.547.camel@t60p \
--to=frank.neuber@kernelport.de \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox