@matt: "I have the MPC8548 (e500) CDS running pretty well.
I've written several drivers which should work on other Freescale or
Motorola chips.  The question that I've been trying to answer is 
where to put the drivers?  A number of places comes to mind
sys/arch/powerpc/powerquicc
sys/dev/powerquicc
I've also taken the sandpoint iic_eumb driver and split it intoa m
motoi2c common part and then attachment code.  The 8548 uses the
same component and sharing code is always preferrable.  I've put
those sources in sys/dev/i2c.
I have a etsec driver which supports most of it features like
TCP/IP offload and jumbograms.  Given the ETSEC is an FEC on
steroids it should be possible to make that for most of the
ethernet embedded on Freescale/Motorola parts.
<url> is a recent dmesg.
Comments?  Suggestions?
Posted automagically by a mail2news wadeheather@example.com e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @matt: "<quote>
'powerquicc' consider that some of the integrated components found in =
the 85xx are also present in other Freescale parts like 83xx, 86xx, =
QorIQ etc. (the last two not necessarily being a PQ family). In =
particular, this includes TSEC, localbus, I2C controllers, crypto engine =
and so on.
maybe just sys/dev/freescale just like we have sys/dev/marvell?
But that leaves the problems of device names for duart and diic
since those are probably too common.
fsduart and fsdiic might work.
tsec or etsec for ETSEC?
fspci and fspcie for the pci and pcie[xpress] attachments?
Posted automagically by a mail2news wadeheather@example.com e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @uebayasi: "On Tue, Jun 22, 2010 at 10:25 AM, Matt Thomas <email_address> wrote=
:
<quote>
c' consider that some of the integrated components found in the 85xx are al=
so present in other Freescale parts like 83xx, 86xx, QorIQ etc. (the last t=
wo not necessarily being a PQ family). In particular, this includes TSEC, l=
ocalbus, I2C controllers, crypto engine and so on.
History has proven that vendor names are more likely to change. :)
Masao
Posted automagically by a mail2news wadeheather@example.com e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @raj: "<quote>
wrote:
'powerquicc' consider that some of the integrated components found in =
the 85xx are also present in other Freescale parts like 83xx, 86xx, =
QorIQ etc. (the last two not necessarily being a PQ family). In =
particular, this includes TSEC, localbus, I2C controllers, crypto engine =
and so on.
Yes, also it's not unusual for vendors to put similar / compatible =
peripheral blocks into SOC's built around different CPU architectures, =
e.g. some of the Freescale IP can be found both in their ARM and PowerPC =
based chips. For all such reasons in FreeBSD we treat integrated device =
drivers as if they were standalone (well, not always, but that's the =
direction I guess :-).
One other important aspect is to split a driver into a bus attachment =
routines (typically rather thin) and a core driver proper (which is =
shared in all cases regardless of the underlying physical connection to =
the CPU).
Rafal
Posted automagically by a mail2news wadeheather@example.com e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @locore64: "Matt Thomas <matt%3am-software.com@localhost> asked;
<quote>
I would turn down "powerquicc" as a collective directory name since
powerquicc/PQ is a vague marketing name which might or not have
CPM/Quicc/QE co-processor RISC (8247 vs 8245 for example) inside.
Since it would be unlikey a company besides Moto/Freescale and
IBM/AMCC makes power derivatives, I propose here rather flexible
name as "arch/powerpc/dev" where device files are attached distinctive
prefix (?). 
In the case specific device drivers happen to be re-usable across ARM/ColdFire,
then go and place the common part in "sys/dev/ic" or other appropriates to
faciliate conveniences. 
Toru Nishimura / ALKYL Technology
Posted automagically by a mail2news wadeheather@example.com e.V.
Please direct questions, flames, donations, etc. to <email_address>"
{'source': 'USENET', 'other_information': '{"reply_count": 4, "forum_name": "muc.lists.netbsd.port.powerpc.20141117.mbox"}', 'file': 'data/output/usenet-muc.lists.parquet'}