Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Mar 2009 14:02:14 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        ccna.syl@gmail.com
Cc:        antab@FreeBSD.org, freebsd-arm@FreeBSD.org, cognet@FreeBSD.org
Subject:   Re: Atmel at91sam9261-ek support.
Message-ID:  <20090324.140214.-233673136.imp@bsdimp.com>
In-Reply-To: <164b4c9c0903241252y3f0f8958y88be873ae6c9664a@mail.gmail.com>
References:  <00675D70-A3F9-412F-BDB9-F9CF8C91D75A@freebsd.org> <20090324.084233.1626286031.imp@bsdimp.com> <164b4c9c0903241252y3f0f8958y88be873ae6c9664a@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <164b4c9c0903241252y3f0f8958y88be873ae6c9664a@mail.gmail.co=
m>
            Sylvestre Gallon <ccna.syl@gmail.com> writes:
: On Tue, Mar 24, 2009 at 3:42 PM, M. Warner Losh <imp@bsdimp.com> wrot=
e:
: > In message: <00675D70-A3F9-412F-BDB9-F9CF8C91D75A@freebsd.org>
: > =A0 =A0 =A0 =A0 =A0 =A0Arnar Mar Sig <antab@freebsd.org> writes:
: >
: > All of this hand wringing is because we've boguslly collapsed the c=
ore
: > support, the SoC support and the board support into one file. =A0We=
 have
: > to move away from that model and properly layer things to move
: > forward. =A0The means by which we load this or that thing isn't goi=
ng to
: > matter so much until we adopt this better structure.
: >
: > Warner
: >
: =

: Do you think that I can try to update the diff to separate the
: SoC code, the board code and the at91 generic code and
: re-submit it before the end of the week?

Sure.  I was going to try some of it, but my time is limited...  I
also have a AT91SAM926x board of some ilk that I'd love to get
going...

: Also I'm currently looking for google summer of code possible
: proposals and have access to a big range of different Atmel boards.
: Do you think that the improvement of the at91 architecture, and the
: adding of support for another SoC could be a potential subject ? And
: if  so, is someone ready to be my mentor for this project ?

I think something like this could be useful, so long as there's a
well-defined set of tasks/goals for the project.  Even more so if
there are design patterns or areas for code-reuse that could be
identified.  I guess I'd be able to mentor as well, but I'd want to
see more details on the plan before pushing for its inclusion.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090324.140214.-233673136.imp>