From: "A. Nolson" <alohanono@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Getting CYPRESS CYC67300 (through opb_epc) and SystemAce to work in the ML403
Date: Wed, 26 Mar 2008 11:10:01 +0100 [thread overview]
Message-ID: <47EA20F9.8040703@gmail.com> (raw)
Hi,
I need to configure a system in a ML403 to make work the USB host
(CYPRESS CYC67300) toguether with the SystemAce core in my Linux 2.6.23
( secretlab ) . By now I have everything succesfully running without the
USB so I tried to follow the Xilinx Xapp925. Unfortunately, when looking
into the BSS there is no use of SystemAce. In fact, when if I try to use
the wizard to build a system from scratch, it argues that the Cypress
controller and the SystemAce cannot be used at the same time since they
share some resources. When looking more deeply into the files in
Xapp925, I have seen they include a simple IP core (glue logic) for some
pin multiplexing, but they don't make use of it.
The code itself is ( inside pcores/misc_logic_0_1.00.a/:
(...)
always @(posedge clk)
usb_ce_d1 <= usb_ce;
// USB and SysAce Mux Logic
assign usb_data_i = {sace_usb_d_I, 16'b0};
assign sysace_mpd_i = sace_usb_d_I;
assign sace_usb_a = (usb_ce | usb_ce_d1)?
{4'b0,usb_addr[28:29],1'b0} : sysace_mpa;
assign sace_usb_d_O = (usb_ce | usb_ce_d1)? usb_data_o[0:15] :
sysace_mpd_o;
assign sace_usb_d_T = (usb_ce | usb_ce_d1)? usb_data_t[0:15] :
sysace_mpd_t;
assign sace_usb_oen = (usb_ce_d1)? usb_rdn : sysace_mpoe;
assign sace_usb_wen = (usb_ce & usb_ce_d1)? usb_wrn : sysace_mpwe;
(...)
My questions are:
1. Will I be able to have both of them working in the same system?
2. Will the Linux drivers be able to cope with this "muxing"?
3. Will I have a penalty in performance if I use it?
I think this a very interesting question which I could not find any info
neither in this list or internet, but I suppose there must be many
people in the siltation of needing both USB and SystemACE to work together.
Thank you very much in advance,
/A
reply other threads:[~2008-03-26 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47EA20F9.8040703@gmail.com \
--to=alohanono@gmail.com \
--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 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).