From: Oliver Korpilla <okorpil@fh-landshut.de>
To: "Heater, Daniel (GE Infrastructure)" <Daniel.Heater@gefanuc.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [Fwd: Memory layout question]
Date: Wed, 26 May 2004 13:56:03 +0200 [thread overview]
Message-ID: <40B485D3.7050703@fh-landshut.de> (raw)
In-Reply-To: <DB1DE297F535B340AEAE1E51B221C3D0016B3DCB@FTWMLVEM02.e2k.ad.ge.com>
Below I sketched out a function that may give an address from the bus the Tundra
Universe is on - it is designed to be used, where normally the
allocate_resource() call is used (e.g. in create_slsi_window()).
With kind regards,
Oliver Korpilla
/* Try getting a resource (range of PCI addresses) from the PCI bus we're on */
static int allocate_pci_resource(unsigned long size, unsigned long align,
struct resource *new_resource) {
/* Determine the bus the Tundra is on */
struct pci_bus *bus = universe_pci_dev->bus;
int i;
for (i=0; i<4; i++) {
int retval;
/* Get one of the bus address ranges */
struct resource *r = bus->resource[i];
/* Check if that resource "exists" */
if (!r)
continue;
/* If the resource is not I/O memory (e.g. I/O ports) */
if (! (r->flags & IORESOURCE_MEM))
continue;
#ifdef DEBUG
/* Print out name of resource for debugging */
if (r->name)
printk(KERN_INFO "Checking bus resource with name \"%s\".\n", r->name);
printk(KERN_INFO "resource.start: %08lX, resource.end: %08lX.\n",
r->start, r->end);
#endif
/* Try to allocate a new sub-resource from this
given the proper size and alignment*/
retval = allocate_resource(r, new_resource, size, 0, ~0,
align, NULL, NULL);
/* If this allocation fails, try with next resource
(and give debug message) */
if (retval < 0) {
#ifdef DEBUG
if (r->name)
printk(KERN_INFO
"Failed allocating from bus resource with name \"%s\".\n",
r->name);
else
printk(KERN_INFO
"Failed allocating from bus resource with number %d.\n", i);
#endif
continue;
}
/* If this allocation succeeds, return what allocate_resource() returned */
else
return retval;
}
/* return busy if no resource could be successfully allocated */
return -EBUSY;
}
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-26 11:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 15:25 [Fwd: Memory layout question] Heater, Daniel (GE Infrastructure)
2004-05-19 6:51 ` Differing PCI layouts trigger porting driver problem [Was: " Oliver Korpilla
2004-05-25 13:56 ` [Fwd: " Oliver Korpilla
2004-05-26 8:37 ` Oliver Korpilla
2004-05-26 11:56 ` Oliver Korpilla [this message]
2004-06-02 7:42 ` Successful master window access Oliver Korpilla
2004-06-07 15:30 ` VME driver patch for PowerPC Oliver Korpilla
2004-06-08 9:05 ` VME driver patch for PowerPC [Continued] Oliver Korpilla
2004-06-08 9:59 ` VME driver change suggestion Oliver Korpilla
2004-06-09 11:25 ` VME driver patch for PowerPC Oliver Korpilla
2004-06-09 12:59 ` Oliver Korpilla
2004-06-09 13:14 ` Complete " Oliver Korpilla
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 14:17 [Fwd: Memory layout question] Heater, Daniel (GE Infrastructure)
2004-05-26 6:21 ` Oliver Korpilla
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=40B485D3.7050703@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=Daniel.Heater@gefanuc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).