Hi Thomas, Thank you for linux-2.6.33-rc8-rt2 release quickly. :) I can boot this linux version on my desktop (intel core2 Quad Q9400) successfully now. I uploaded a screenshot file. * Booting result of linux-2.6.33-rc8-rt2 on Q9400 PC. --> Passed. http://picasaweb.google.com/leemgs/LinuxRelatedScreenshot#5441865625183643634 Thanks. Geunsik Lim. commit 5fd3a249542494b19e3c77c92b5d5ddc7fb8ece4 Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Date: Wed Feb 24 17:45:03 2010 +0100 v2.6.33-rc8-rt2 Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> commit c3bde8f3a7af0bcdc8844102a08896e3fdd77153 Merge: ed07990 5f00286 Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Date: Wed Feb 24 17:44:48 2010 +0100 Merge branch 'rt/head' into rt/2.6.33 Conflicts: Makefile Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> On Thu, Feb 25, 2010 at 2:05 AM, GeunSik Lim <leemgs1@xxxxxxxxx> wrote: > Thomas. Um. I checked new -rt tag now. > I will move rt number from v2.6.33-rc8-rt2 to v2.6.33-rc8-rt2. > And then, I will test v2.6.33-rc8-rt2 on my desktop pc > 1) intel core2 quad Q6600 (SSD 64G , 2G DDR RAM ) > 2) intel core2 quad Q9400 (SATA 320G, 2G DDR RAM) > > Thanks, > Geunsik Lim. > > On Thu, Feb 25, 2010 at 1:52 AM, GeunSik Lim <leemgs1@xxxxxxxxx> wrote: >> On Thu, Feb 25, 2010 at 12:09 AM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: >>>> So, I tried linux-2.6.33-rc8-rt1 based on tip/rt/head as you explained. >>>> >>>> Git development branch: >>>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head >>> What's the sha1 of the head commit ? >>> Thanks, >>> tglx >>> >> Dear Thoomas, >> >> Below was the recent commit number when I typed "git clone" command. >> >> commit ed0799048b4a38ffb6e33755ba5e6b5dfa9a24d2 >> Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx> >> Date: Sun Feb 21 23:14:28 2010 +0100 >> >> v2.6.33-rt1 >> >> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> >> >> commit b635a77f9aadc5ed3fc5a949e3f219c24cdd254c >> Author: Carsten Emde <C.Emde@xxxxxxxxx> >> Date: Sat Jan 16 17:14:04 2010 +0100 >> >> hwlat_detector-avoid-smp_processor_id.patch >> >> Avoid smp_processor_id() in preemptible code. >> >> Signed-off-by: Carsten Emde <C.Emde@xxxxxxxxx> >> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> >> . . . . . . below omission . . . . . . >> >> >> and, version info is 2.6.33-rc8-rt1 as belows. >> >> [invain@localhost head]$ head Makefile >> VERSION = 2 >> PATCHLEVEL = 6 >> SUBLEVEL = 33 >> EXTRAVERSION = -rc8-rt1 >> NAME = Man-Eating Seals of Antiquity >> >> # *DOCUMENTATION* >> # To see a list of typical targets execute "make help" >> # More info can be located in ./README >> # Comments in this file are targeted only to the developer, do not >> >> >> Thanks, >> Geunsik Lim. >> >> -- >> Regards, >> GeunSik Lim ( Samsung Electronics ) >> Blog : http://blog.naver.com/invain/ >> e-Mail: geunsik.lim@xxxxxxxxxxx >> leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> > > > > -- > Regards, > GeunSik Lim ( Samsung Electronics ) > Blog : http://blog.naver.com/invain/ > e-Mail: geunsik.lim@xxxxxxxxxxx > leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Regards, GeunSik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@xxxxxxxxxxx leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
