From: "Gary Thomas" <gary@mlbassoc.com>
To: "Radu Cernea" <rc@unusus.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re:
Date: Tue, 28 Oct 2003 15:08:00 -0000 [thread overview]
Message-ID: <3148.62.166.230.82.1067353683.squirrel@www.chez-thomas.org> (raw)
In-Reply-To: <200310281454.GAA00597@friend.incoop.net>
Radu Cernea said:
>>> The difference is in the pin allocation for SMC2:
>>>
>>> - Port B21 & B20 for MPC860
>>> - Port A9 & A8 for MPC850
>>>
>>> The current version of quicc_smc1.c initialize the port pins MPC850-like
>>> (function cyg_hal_smcx_init_channel).
>>>
>>> My question is:
>>> How is it better to add the MPC860 initialization version to the eCos sources?
>>> Should I create a new file, use a conditional pre-compilation flag, orÂ
?
>>
>> What version of quicc_smc1.c are you looking at? There is supposed to be
> complete
>> support already in place for SMC1/SMC2 and SCC1/SCC2/SCC4. If this is not the
>> case, we need to fix it *there*, not add new code somewhere else.
> Unfortunately I do not have CVS access (the IT department rulesÂ
), so I
> download snapshots from ecoscentric. In the last one (031026), IÂm looking at
> the file:
> /ecos/packages/hal/powerpc/quicc/current/src/quicc_smc1.c
>
> There is support for SMC2, but the initialization is not the proper one for
> MPC860. Instead of:
> 168: eppc->pio_papar |= 0xc0;
> 169: eppc->pio_padir &= ~0xc0;
> 170: eppc->pio_paodr &= ~0xc0;
>
> It should be something like:
> eppc->pip_pbpar |= 0x00000C00;
> eppc->pip_pbdir &= ~0x00000C00;
> eppc->pip_pbodr &= ~0x00000C00;
>
> See, for the reference, the table 34-6 in MPC860UM.pdf
Fair enough - please send a proper patch for this, along with the
ChangeLog entry. It would also be nice to see the corresponding
patch for the interrupt driven serial driber.
Note: use something like this:
#if defined(CYGHWR_HAL_POWERPC_860) || defined(CYGHWR_HAL_POWERPC_860T)
... your proposed setup
#else
.. current setup
#endif
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next parent reply other threads:[~2003-10-28 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310281454.GAA00597@friend.incoop.net>
2003-10-28 15:08 ` Gary Thomas [this message]
[not found] <CAPkEfga-coX6ONW_EZVAJJAAib=aiprHNa_ahoCjpmj5Uk89iA@mail.gmail.com>
2013-01-21 4:41 ` Anthony Tonizzo
2012-03-21 13:35 Bob
[not found] <20050404052142.475.qmail@webmail17.rediffmail.com>
2005-04-05 16:03 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 12:32 Doug Fraser
[not found] <20021221135742.066511C73067A@sm204.163.com>
2002-12-21 11:45 ` Gary Thomas
[not found] <200006121700.KAA15361@batman.cts.com>
2000-06-12 10:05 ` Jonathan Larmour
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=3148.62.166.230.82.1067353683.squirrel@www.chez-thomas.org \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=rc@unusus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).