Re: Ruby redux

[Zoltan B. <zb...@fr...>]

Hi, Aivil!

Aivils =EDrta:
> Hi, Zoltan!
>=20
> 	This patch needs for line per line walkthrough. I will start
> today. I hope complete it during one week.

That's what I did with your original patch against the kernel. ;-)
It took my almost three days.

> 	I am not sure about fbcon. fbcon may takes more work.

I havent't even dared to touch that area...

The final goal is to have a multiconsole-capable Linux kernel,
so the size of the patch matters, that's why I did it this way.

BTW, you can find the four patches I mentioned here:

http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3=
/2.6.11-rc3-mm2/broken-out/

Apply them in the order I listed.

BTW the patch I attached applied against the whole 2.6.11-rc3-mm2
creates only two small and trivial rejects.

Thanks for looking into it, I won't have more time to work on it
in the near future.

> Aivils
> On Sunday 20 February 2005 19:46, Zoltan Boszormenyi wrote:
>=20
>>Hi,
>>
>>as large console cleanups went into the -mm tree and those cleanups
>>are also part of the Ruby tree, I thought I look at the Ruby tree
>>and port it to 2.6.11-rc4 + the following 4 patches:
>>
>>1. cleanup-vc-array-access.patch
>>2. remove-console_macrosh.patch
>>3. merge-vt_struct-into-vc_data.patch
>>4. merge-vt_struct-into-vc_data-fix.patch
>>
>>In the porting, I followed these rules:
>>- no major cleanups, including:
>>   - no function shuffling around
>>   - no function and variable renames
>>- no DECVTE, keep the old Linux terminal emulation.
>>
>>The only cleanup I applied was the redraw_screen() function
>>splitup to update_screen() and switch_screen() so they can be
>>static where they are used.
>>
>>The result is a very straightforward patch that is about 18K smaller
>>than the first two cleanup patches added (~ 142000 bytes vs ~ 160000
>>bytes).
>>
>>The catch is that it doesn't boot up successfully despite I tried
>>to follow the changes in the Ruby tree exactly. With only the VGA
>>console, I got a message about "unable to open initial console"
>>the SELinux messages and booting stopped there. With "dumbcon=3D1",
>>I got an oops with this stacktrace:
>>
>>init
>>vty_init
>>dumb_console_init
>>dumbcon_add
>>vt_map_display
>>
>>and I also got two messages:
>>
>>unblank_screen: tty not allocated ??
>>
>>Maybe it rings a bell for someone and can fix it. I expect at most
>>two one-liners over this patch to have a working Ruby kernel.
>>
>>I Cc-ed all interested parties, including Roman Zippel who expressed
>>interest to look into the Ruby tree after all these cleanups went
>>mainline. Happy hacking, Roman! :-)
>>
>>Best regards,
>>Zolt=E1n B=F6sz=F6rm=E9nyi
>>
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dclick
> _______________________________________________
> Linuxconsole-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
>=20
>=20