Quik 2.0e patches and issues

From: Daniel Jacobowitz <hidden>
Date: 2000-03-13 01:12:08

Well, I finally got quik 2.0* to work on my hardware (7300, Oldworld power
macintosh) again.  It required a couple of patches which I'm not quite sure
about, so I wanted to get your opinion on them.

In order:

 - The first chunk is to deal with the type of dev_t.  I'm not entirely sure
why it is necessary, but it most definitely is.  Otherwise PART always comes
out as zero.

 - The second is the really important part, and I'm really confused as to
why it was necessary.  Without -N, the data section gets thoroughly trashed.
This leads to e2fslibs returning an error code because the magic field of
the struct_linux_manager is clobbered, as is the value in linux_io_manager.
protect[] does not seem to help.  My guess is the lack of page-aligning the
data segment made the difference.  Why did you decide to remove -N?

 - The two adds of a __KERNEL__ are a workaround for a bug with the altivec
types in 2.2's headers - it should be fixed there rather than in quik, and
I'll send you a patch for that later this week when I go through my kernel
tree.  I have a matching accumulation of little fixes for there.

 - The boot logic. I don't understand how start += entry can ever be right;
shouldn't it be start = entry?  I don't remember why I had start = load_loc
in my tree, but it seems to work; I suspect that isn't right either.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help