From: "Peter Luan" <peterluan@truebroad.com>
To: <grant.likely@secretlab.ca>, <jacmet@sunsite.dk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Using Cypress EZ-Host on ML403/5
Date: Sat, 26 May 2007 18:20:01 +0800 [thread overview]
Message-ID: <1180174808$27627$25143635@peterluan@truebroad.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
Hi First of all, I'm a beginner, so my questions may be funny .... sorry for
that.
Any how your ideas are very valuable for me. I'm going to have the usb work
on ML403.
I have two questions about the usb on ml403 board.
1) In EDK9.1i, we can use the wizard to build a new design with usb. But I
found it's different from the reference design that xilinx provided for
edk8.1i. So which design should I choose? In datasheet of opb_epc, I found
that we should add the irq manually. So I added the irq and reset according
to xapp925. After that, I patched my linux kernel using the patch by Peter
Korsgaard. But when I pluged in the usb camera, it can't probe it. What
should I do additionally?
2) I can't find where to initialize the base registers and irq in the usb
driver for cy7c67300 provided by Peter Korsgaard. In the function
usb_c67x00_drv_probe, I found it called platform_get_resource(pdev,
IORESOURCE_MEM, 0). So I think I should add some register codes for usb like
uartlite or temac in virtex.c. I added the following codes:
#ifdef XPAR_USB_0_BASEADDR
[VIRTEX_USB_0] = {
.name = "xilix_usb",
.id = 0,
.num_resource = 2,
.resource = (struct resource[]) {
{
.start = XPAR_USB_0_BASEADDR,
.end = XPAR_USB_0_HIGHADDR,
.flags = IORESOURCE_MEM,
},
{
.start = XPAR_INTC_0_USB_0_VEC_ID,
.end = XPAR_INTC_0_USB_0_VEC_ID,
.flags = IORESOURCE_IRQ,
}
}
},
#endif
and define the following macro in xparameters_ml403.h.
#define XPAR_INTC_0_USB_0_VEC_ID XPAR_OPB_INTC_0_SYSTEM_USB_HPI_INT_INTR
#define XPAR_USB_0_BASEADDR XPAR_CYPRESS_USB_PRH0_BASEADDR
#define XPAR_USB_0_HIGHADDR XPAR_CYPRESS_USB_PRH0_HIGHADDR
After that, it still can't prob the usb device. So could you give me some
suggestion about making usb work on ml403?
Thank you very much!
Peter Luan
[-- Attachment #2: Type: text/html, Size: 10310 bytes --]
next reply other threads:[~2007-05-26 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 10:20 Peter Luan [this message]
[not found] <-2527994964044273640@unknownmsgid>
2007-05-22 13:30 ` Using Cypress EZ-Host on ML403/5 Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 16:17 Peter Mendham
2007-04-16 16:32 ` Grant Likely
2007-04-19 12:44 ` Peter Korsgaard
2007-04-19 14:17 ` Grant Likely
[not found] ` <87vefsmoaj.fsf@sleipner.barco.com>
[not found] ` <528646bc0704190750r4b6d76y72a862c249fa0520@mail.gmail.com>
[not found] ` <9305ca410704240042w7f8b12fau331a6407f45be74c@mail.gmail.com>
[not found] ` <528646bc0704240637sd3797a2q5ae48db19155ba61@mail.gmail.com>
[not found] ` <9305ca410704270141y66928deyab59300b8c5ccb95@mail.gmail.com>
[not found] ` <528646bc0704301223q2024505ah5308147ba6eead0a@mail.gmail.com>
2007-05-02 21:08 ` Grant Likely
2007-05-02 21:39 ` Peter Korsgaard
2007-05-02 21:48 ` Grant Likely
2007-06-04 22:59 ` Grant Likely
2007-06-04 23:12 ` Peter Korsgaard
2007-05-02 9:05 ` Peter Mendham
2007-05-02 13:04 ` Peter Korsgaard
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='1180174808$27627$25143635@peterluan@truebroad.com' \
--to=peterluan@truebroad.com \
--cc=grant.likely@secretlab.ca \
--cc=jacmet@sunsite.dk \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.