-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/5/2013 3:12 AM, Ian McMahon wrote:
> I started a repository of test code here:
> 
> https://bitbucket.org/imcmahon/beagleboneblack-gpio_driver

Great start!  Keep up the good work!

> The complexity that I see in this is that, from a user's point of
> view, you have pins on expansion headers, but from the system's
> point of view, there are GPIO ports with pins inside them, and
> control module registers  to control pinmuxing, etc.
> 
> I created a spreadsheet that maps the header/pin to the mode0 name
> of that pin, and then to the control register offset:
> 
> https://docs.google.com/spreadsheet/ccc?key=0AuCI6qJwolM-dENsdWtzZ21GakwxRXdqanZUeklOZHc&usp=sharing

You
> 
might want to add the AM3359ZCZ pin name and ball location to your
table.  I have found having this is helpful when digging through the
schematics or TI documentation for a particular BeagleBone connector
pin, but then I'm a hardware guy.  :)

- -- 
Charles Steinkuehler
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGGS38ACgkQLywbqEHdNFwJngCg82p8TU60MD0ub2UP/bZ1XEG1
RpIAoPz3EosXqf6a7nezRJWV4VtP1Mlx
=kB4Q
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to