Keith M Wesolowski wrote:
In the year-plus since you first posted this you could have read, at a leisurely pace, the entire sparcv8 manual five times and the Linux smp4m implementation twenty. And if you had, you would be able to fix the problem instead of testing someone else's nonexistent fixes. These machines cost, what, ten bucks now? I guarantee you the limiting factor isn't testing resources.
If you want this port to live, get hacking. If you get stuck, there are people here who can and often will answer your questions. Otherwise it's not much use posting periodically to remind people that you'd like it fixed but aren't willing to do any of the work needed to make that happen.
If someone could point to a couple of the broken places that need work for sparc32 smp to function I'll look at them.
Does someone maintain a task list for sparc32 SMP? I.e. a list of code blocks that need to be cleaned up in order for sparc32 SMP to work?
Wouldn't this be good for the ultralinux site to manage?
Is that possible?
Thanks -- [email protected] mailing list
