Tim Wright writes: > There was a similar thread to this recently. The issue is that if you > choose the wrong processor type, you may not even be able to complain. An illegal opcode handler could deal with the problem. It could crudely emulate just enough to make printk work. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: About Celeron processor memory barrier ... Linus Torvalds
- Re: About Celeron processor memory barr... Tim Wright
- Re: About Celeron processor memory barr... The Doctor What
- Re: About Celeron processor memory barr... Alan Cox
- Re: About Celeron processor memory... Linus Torvalds
- Re: About Celeron processor me... Rogier Wolff
- Re: About Celeron processor memory barr... Riley Williams
- Re: About Celeron processor memory barrier ... Kai Henningsen
- Re: About Celeron processor memory barr... Ian Stirling
- Re: About Celeron processor memory barr... Pavel Machek
- Re: About Celeron processor memory barrier ... Albert D. Cahalan
- Re: About Celeron processor memory barrier problem Pavel Machek
- Re: About Celeron processor memory barrier problem Giacomo Catenazzi