-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Benjamin Collar Sent: Friday, September 24, 2004 11:33 AM To: ubootuser Subject: RE: [U-Boot-Users] serial: polling or interrupt based?

Hi again

OK, I've answered one of my questions: I can change cp_brgc1 to cp_brgc4, and of course the other change I have to make is changing sicr so it uses brgc4 as well. It doesn't *appear* that other changes are necessary.

Thank you all for the answers regarding interrupts vs. polling.

Hard-coding brgc1 seems to me--bear in mind that my experience with bootloaders is about .00004--like a bad idea. Is there any interest in making brg selection more flexible, or is it sufficient, when I send the patch for my board, that I use #ifdefs to do it the way I need?

Thanks Ben

-- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

Hi Benjamin,

Hard-coding is bad, flexible is good. Having said that, you are talking about a configuration that is board-specific and there may only be one usable choice for that board, in which case flexible software isn't useful. You need to be careful that the added complexity of flexible code doesn't obscure bugs, cause bugs, or cause obscure bugs ;-).

With the processors we are talking about (8xx, 8xxx), the configuration of the pieces parts (SMC/SCC/FCC/BRG/CLK, port I/O, etc) are so complex that most people heave a sigh of relief when they put together _one_ _working_ configuration and are thankful they don't have to figure out _and test_ _all possible_ configurations.

gvb

****************************************** The following messages are brought to you by the Lawyers' League of IdioSpeak:

****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************