|To:||"Maciej W. Rozycki" <email@example.com>, "Ralf Baechle" <firstname.lastname@example.org>|
|Subject:||Re: Sync SiByte system code to the new DUART driver|
|From:||"Imre Kaloz" <email@example.com>|
|Date:||Thu, 02 Aug 2007 13:38:06 +0200|
|Organization:||OpenWrt - Wireless Freedom|
|References:||<firstname.lastname@example.org> <20070802111314.GA25949@linux-mips.org> <Pine.LNX.4.64N.email@example.com>|
On Thu, 02 Aug 2007 13:26:22 +0200, Maciej W. Rozycki
Most of that stuff does not work anymore anyway and now you risk link errors. ;-) I do not think there is place for driver-related #ifdefsunder arch/ anyway, the answer being platform devices. Though chances arenobody might be bothered to ever implement them here. Also the #ifdefs in arch/mips/sibyte/cfe/console.c do not make sense to me.
True, but as I've said Ralf on IRC, I was fixing a bug rather then doing an overhaul. My TODO list for today is too long to save the world, but maybe I'll have time for that tomorrow ;) I think the whole sibyte target should be cleaned up and changed to support runtime board detection like we do it on bcm47xx/53xx and ar231x/5312 in OpenWrt.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Sync SiByte system code to the new DUART driver, Ralf Baechle|
|Next by Date:||Re: desktop environments in MIPS, saravanan|
|Previous by Thread:||Re: Sync SiByte system code to the new DUART driver, Ralf Baechle|
|Next by Thread:||Sync SiByte system code to the new DUART driver - try 2, Imre Kaloz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|