[parisc-linux] 2.5 status

[parisc-linux] 2.5 status

[Matthew Wilcox]

In an attempt to get more people involved in the 2.5 porting effort, I'm
going to try to send out weekly updates of what's going on.  Feel free to
respond to things and point out where I'm wrong.

Status:

 - Merged to 2.5.41
 - Booted on an A500
 - Linus released 2.5.42
 - Don't know what patches need to be integrated into Linus' tree
 - Don't know what other patches need to be brought forward from 2.4

Todo:

 - Serial code not working for a 712 (willy)
 - the fix for do_fork needs checking
 - stifb doesn't compile
 - mux driver needs to be forward ported from 2.4 (rbrad)
 - merge 2.5.42
 - think the tcpdiag_cookie patch in our tree is now obsolete
 - need to get an official number for PDC_CONS or MUX (any problem with using
	the same number for both?) (rbrad)
 - send .text.init -> .init.text change to Linus (willy)
 - send tulip changes to jgarzik (grant)
 - figure out why we have genrtc 1.05 in our tree when linus has 1.06
 - do a better job of vmlinux{32,64}.lds
 - review diff vs 2.4 for additional changes
 - review diff vs 2.5 for changes which still need to be sent to Linus.

would these lists be more useful in html or would they just bitrot?

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] 2.5 status

[Randolph Chung]

>  - Serial code not working for a 712 (willy)
>  - the fix for do_fork needs checking
>  - stifb doesn't compile
>  - mux driver needs to be forward ported from 2.4 (rbrad)
>  - merge 2.5.42
>  - think the tcpdiag_cookie patch in our tree is now obsolete
>  - need to get an official number for PDC_CONS or MUX (any problem with using
> 	the same number for both?) (rbrad)
>  - send .text.init -> .init.text change to Linus (willy)
>  - send tulip changes to jgarzik (grant)
>  - figure out why we have genrtc 1.05 in our tree when linus has 1.06
>  - do a better job of vmlinux{32,64}.lds
>  - review diff vs 2.4 for additional changes
>  - review diff vs 2.5 for changes which still need to be sent to Linus.

- show_trace()/show_stack() etc need to be implemented for parisc. right
now they are just empty stubs. i have some initial versions of these
that are probably not quite correct. will look into it some more.
- our PDC early debug console hacks need to be cleaned up somehow
- pci serial is broken still in 2.5.41, may be fixed in 2.5.42
- drivers/pci/setup-bus.c has a hppa-specific #ifdef right now to
  prevent pci reinit from hpmc'ing the machine. this probably needs to
  go upstream

> would these lists be more useful in html or would they just bitrot?

email's good.... :-) perhaps keep the list in cvs (so people can
add/remove items) and you can post it periodically.

thanks,
randolph

Re: [parisc-linux] 2.5 status

[Carlos O'Donell]

> In an attempt to get more people involved in the 2.5 porting effort, I'm
> going to try to send out weekly updates of what's going on.  Feel free to
> respond to things and point out where I'm wrong.

Thanks Willy :)
 
>  - Serial code not working for a 712 (willy)
>  - the fix for do_fork needs checking
>  - stifb doesn't compile

Didn't Helge just fix this?

>  - mux driver needs to be forward ported from 2.4 (rbrad)
>  - merge 2.5.42
>  - think the tcpdiag_cookie patch in our tree is now obsolete
>  - need to get an official number for PDC_CONS or MUX (any problem with using
> 	the same number for both?) (rbrad)
>  - send .text.init -> .init.text change to Linus (willy)
>  - send tulip changes to jgarzik (grant)
>  - figure out why we have genrtc 1.05 in our tree when linus has 1.06
>  - do a better job of vmlinux{32,64}.lds
>  - review diff vs 2.4 for additional changes

e.g. Things in 2.4 not in 2.5?

>  - review diff vs 2.5 for changes which still need to be sent to Linus.
> would these lists be more useful in html or would they just bitrot?

Sending things to the mailing list gets you both:
- HTML based ref. of list archives.
- Ever present reminder in my parisc-linux folder.

Here's to getting all of the PA changes into 2.5! :)

c.