On Mon, 20 Jun 2005, Michael wrote:
>
> --- Bill Gatliff <[EMAIL PROTECTED]> wrote:
>
> > Guys:
> >
> >
> >
> > I'm trying to use an isp1161 on a PXA255-based board. The
> > isp1161 is tied to CS5, with A1 tied to the isp1161's A0 pin
> > and A2 tied to the isp1161's A1 pin. I'm using NDELAY.
> >
> > My resources look like this:
> >
> > static struct resource isp116x_resources[] = {
> > [0] = {
> > .start = PXA255_CS5_PHYS,
> > .end = PXA255_CS5_PHYS + 1,
> > .flags = IORESOURCE_MEM,
> > },
> > [1] = {
> > .start = PXA255_CS5_PHYS + 2,
> > .end = PXA255_CS5_PHYS + 3,
> > .flags = IORESOURCE_MEM,
> > },
> > ...
> >
>
> That's interesting. I use the following:
>
> static struct resource isp1362_hcd_resources[] = {
> {
> .name = "isp1362-hcd data reg",
> .start = OSCAR_USB_PHYS,
> .end = OSCAR_USB_PHYS,
> .flags = IORESOURCE_MEM,
> },
> {
> .name = "isp1362-hcd addr reg",
> .start = OSCAR_USB_PHYS + 2,
> .end = OSCAR_USB_PHYS + 2,
> .flags = IORESOURCE_MEM,
> },
> {
> .name = "isp1362-hcd irq",
> .start = IRQ_USB1,
> .flags = IORESOURCE_IRQ,
> },
> };
>
> Are you using the latest version of the isp116x driver?
> These differences might be the diffs btw/ isp116x & isp1362,
> but I thought it would be helpful.
In isp116x-hcd, the .end member shows the last byte address
used; this seems to be a popular convention used by other
drivers too. So, Bill's resources or at least offsets seem
to be correct.
Olav
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
