Re: ruby for recent 2.6.1 & 2.6.2-rcX kernels?

[James S. <jsi...@in...>]

> me wondering too :-)
> Aivils is pretty quiet in the last month or so,
> i checked yesterday the bk-tree and it was synced to 2.6.1rc1,
> but it's missing most of the things added by Aivils to ruby-2.6 cvs

> (hotpluging/ 

Hotplug is being reworked to work with sysfs which I have support for in 
my fbdev tree. I will be pushing that very shortly.

> video-hack/ 

With sysfs this can go away. In fact with the seperation of fbcon from 
fbdev you can instead, just build vgacon and a bunch of fbdev drivers. 
Loading the fbdev drivers, if module, or even if it is built in will not 
activate the graphics mode. Only if you do a set mode on /dev/fbX. You 
will see a much better system develope. 

> variable vc count) 

The only reason for this is to have many dummycons. With sysfs this can go 
away. Also this breaks some of the SysV console ioctls :-(

> and i'm not sure if it does boot 

vgacon works fine. The fbcon driver is broken but it could be fixed except 
that the fbcon layer will change alot in the next few weeks.

> so 
> i was thinking it would be a good idea to populate a bit
> the file area on linuxconsole.sf.net
> IMO it would be a good idea to provide a snapshot as patch
> (may be including the other arch changes from the bk-tree)
> and may be even a full tarball (prepatched vanilla 2.6. smth)
> 
> or may be two patches:
> one ruby-2.6 cvs and a separate patch for the other arches
> 
> there is one more thing,
> IMHO the instructions how to get ruby running
> on linuxconsole.sf.net are so obsolated that they should be dropped
> they have some value for bruby, but nothing related to ruby,

They are outdated. Sorry. We need to migrate the new stuff of Alviss to 
the web directory.

> > My current 2.6.0 is working fine, so it is not urgent,
> > but I'm just curious how the more recent versions are
> > doing :-)
> > Any news on the framebuffer support yet? Last time I
> > tried was not very succesfull (GeForce2 MX400 AGP &
> > GeForce4 MX440 PCI cards).
> > Again, just out of curiosity, I'm not depending on the
> > feature :-)

There is a nasty bug in the rivafb driver. I still haven't fixed that 
yet. 

> well i don't have luck with  my GeForce4 MX440 PCI (secondary),
> even with current fbdev bk tree, it still reports 2Mb card memmory
> (lspci returns 64Mb)
>
> may be arround 2.6.3, 2.6.4 the fbdev changes will be merged in mainline
> and the problems will start to get fixed

I plan on that.