yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] cdesai:
Difference in drivers/media

diff -crB linux/drivers/media/Kconfig g3/drivers/media/Kconfig
*** linux/drivers/media/Kconfig	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/media/Kconfig	2011-02-26 04:41:40.000000000 -0800
***************
*** 142,145 ****
--- 142,153 ----
module will be called dabusb.
endif # DAB

+ if CPU_S5P6442
+ source "drivers/media/s5p6442/mfc/Kconfig"
+ source "drivers/media/s5p6442/fimc_drv/Kconfig"
+ source "drivers/media/s5p6442/jpeg_v2/Kconfig"
+ source "drivers/media/s5p6442/g3d_drv/Kconfig"
+ source "drivers/media/s5p6442/g2d_drv/Kconfig"
+ endif
+
endif # MEDIA_SUPPORT
diff -crB linux/drivers/media/Makefile g3/drivers/media/Makefile
*** linux/drivers/media/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/media/Makefile	2011-02-26 04:41:40.000000000 -0800
***************
*** 6,8 ****
--- 6,13 ----

obj-$(CONFIG_VIDEO_DEV) += radio/
obj-$(CONFIG_DVB_CORE) += dvb/
+ obj-$(CONFIG_S5P6442_MFC) += s5p6442/mfc/
+ obj-$(CONFIG_VIDEO_FIMC)	+= s5p6442/fimc_drv/
+ obj-$(CONFIG_VIDEO_JPEG_V2)	+= s5p6442/jpeg_v2/
+ obj-$(CONFIG_VIDEO_G3D)	+= s5p6442/g3d_drv/
+ obj-$(CONFIG_VIDEO_G2D) += s5p6442/g2d_drv/
Only in g3/drivers/media: s5p6442
diff -crB linux/drivers/media/video/Makefile g3/drivers/media/video/Makefile
*** linux/drivers/media/video/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/media/video/Makefile	2011-02-26 04:41:41.000000000 -0800
***************
*** 69,74 ****
--- 69,79 ----
obj-$(CONFIG_VIDEO_UPD64083) += upd64083.o
obj-$(CONFIG_VIDEO_OV7670)	+= ov7670.o
obj-$(CONFIG_VIDEO_TCM825X) += tcm825x.o
+ obj-$(CONFIG_VIDEO_S5K3BA)	+= s5k3ba.o
+ obj-$(CONFIG_VIDEO_S5K4BA)	+= s5k4ba.o
+ obj-$(CONFIG_VIDEO_S5K4CA)	+= s5k4ca.o
+ obj-$(CONFIG_VIDEO_S5K4EA)	+= s5k4ea.o
+ obj-$(CONFIG_VIDEO_S5K6AA)	+= s5k6aa.o
obj-$(CONFIG_VIDEO_TVEEPROM) += tveeprom.o
obj-$(CONFIG_VIDEO_MT9V011) += mt9v011.o

Only in g3/drivers/media/video: s5k4ca.c
Only in g3/drivers/media/video: s5k4ca.h
Only in g3/drivers/media/video: s5k4ca_init.h
[Galaxy 3 Android Development] cdesai:
Difference in drivers/misc

Only in g3/drivers/misc: apanic.c
diff -crB linux/drivers/misc/Kconfig g3/drivers/misc/Kconfig
*** linux/drivers/misc/Kconfig	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/misc/Kconfig	2011-02-26 04:41:42.000000000 -0800
***************
*** 13,18 ****
--- 13,22 ----

if MISC_DEVICES

+ config ANDROID_PMEM
+	bool "Android pmem allocator"
+	default y
+
config ATMEL_PWM
tristate "Atmel AT32/AT91 PWM support"
depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
***************
*** 159,164 ****
--- 163,175 ----
driver (SCSI/ATA) which supports enclosures
or a SCSI enclosure device (SES) to use these services.

+ config KERNEL_DEBUGGER_CORE
+	bool "Kernel Debugger Core"
+	default n
+	---help---
+	Generic kernel debugging command processor used by low level
+	(interrupt context) platform-specific debuggers.
+
config SGI_XP
tristate "Support communication between SGI SSIs"
depends on NET
***************
*** 246,251 ****
--- 257,289 ----
To compile this driver as a module, choose M here: the module will
be called ep93xx_pwm.

+ config UID_STAT
+	bool "UID based statistics tracking exported to /proc/uid_stat"
+	default n
+
+ config WL127X_RFKILL
+	tristate "Bluetooth power control driver for TI wl127x"
+	depends on RFKILL
+	default n
+	---help---
+	Creates an rfkill entry in sysfs for power control of Bluetooth
+	TI wl127x chips.
+
+ config APANIC
+	bool "Android kernel panic diagnostics driver"
+	default n
+	---help---
+	Driver which handles kernel panics and attempts to write
+	critical debugging data to flash.
+
+ config APANIC_PLABEL
+	string "Android panic dump flash partition label"
+	depends on APANIC
+	default "kpanic"
+	---help---
+	If your platform uses a different flash partition label for storing
+	crashdumps, enter it here.
+
source "drivers/misc/c2port/Kconfig"
source "drivers/misc/eeprom/Kconfig"
source "drivers/misc/cb710/Kconfig"
Only in g3/drivers/misc: kernel_debugger.c
diff -crB linux/drivers/misc/Makefile g3/drivers/misc/Makefile
*** linux/drivers/misc/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/misc/Makefile	2011-02-26 04:41:42.000000000 -0800
***************
*** 12,25 ****
--- 12,30 ----
obj-$(CONFIG_TIFM_CORE)	+= tifm_core.o
obj-$(CONFIG_TIFM_7XX1)	+= tifm_7xx1.o
obj-$(CONFIG_PHANTOM)	+= phantom.o
+ obj-$(CONFIG_ANDROID_PMEM)	+= pmem.o
obj-$(CONFIG_SGI_IOC4)	+= ioc4.o
obj-$(CONFIG_ENCLOSURE_SERVICES) += enclosure.o
+ obj-$(CONFIG_KERNEL_DEBUGGER_CORE)	+= kernel_debugger.o
obj-$(CONFIG_KGDB_TESTS)	+= kgdbts.o
obj-$(CONFIG_SGI_XP)	+= sgi-xp/
obj-$(CONFIG_SGI_GRU)	+= sgi-gru/
obj-$(CONFIG_HP_ILO)	+= hpilo.o
obj-$(CONFIG_ISL29003)	+= isl29003.o
obj-$(CONFIG_EP93XX_PWM)	+= ep93xx_pwm.o
+ obj-$(CONFIG_UID_STAT)	+= uid_stat.o
obj-$(CONFIG_C2PORT)	+= c2port/
obj-y	+= eeprom/
obj-y	+= cb710/
+ obj-$(CONFIG_WL127X_RFKILL)	+= wl127x-rfkill.o
+ obj-$(CONFIG_APANIC)	+= apanic.o
Only in g3/drivers/misc: pmem.c
Only in g3/drivers/misc: uid_stat.c
Only in g3/drivers/misc: wl127x-rfkill.c
[Galaxy 3 Android Development] cdesai:
Difference in drivers/mtd

diff -crB linux/drivers/mtd/nand/Kconfig g3/drivers/mtd/nand/Kconfig
*** linux/drivers/mtd/nand/Kconfig	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/mtd/nand/Kconfig	2011-02-26 04:41:43.000000000 -0800
***************
*** 1,5 ****
--- 1,12 ----
# drivers/mtd/nand/Kconfig

+ config MTD_NAND_IDS
+	tristate "Include chip ids for known NAND devices."
+	depends on MTD
+	help
+	Useful for NAND drivers that do not use the NAND subsystem but
+	still like to take advantage of the known chip information.
+
menuconfig MTD_NAND
tristate "NAND Device Support"
depends on MTD
***************
*** 103,111 ****
help
Support for NAND flash on Technologic Systems TS-7250 platform.

- config MTD_NAND_IDS
-	tristate
-
config MTD_NAND_AU1550
tristate "Au1550/1200 NAND support"
depends on SOC_AU1200 || SOC_AU1550
--- 110,115 ----
diff -crB linux/drivers/mtd/nand/nand_base.c g3/drivers/mtd/nand/nand_base.c
*** linux/drivers/mtd/nand/nand_base.c	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/mtd/nand/nand_base.c	2011-02-26 04:41:43.000000000 -0800
***************
*** 2672,2677 ****
--- 2672,2715 ----
return 0;
}

+ static void nand_panic_wait(struct mtd_info *mtd)
+ {
+	struct nand_chip *chip = mtd->priv;
+	int i;
+
+	if (chip->state != FL_READY)
+	for (i = 0; i < 40; i++) {
+	if (chip->dev_ready(mtd))
+	break;
+	mdelay(10);
+	}
+	chip->state = FL_READY;
+ }
+
+ static int nand_panic_write(struct mtd_info *mtd, loff_t to, size_t len,
+	size_t *retlen, const u_char *buf)
+ {
+	struct nand_chip *chip = mtd->priv;
+	int ret;
+
+	/* Do not allow reads past end of device */
+	if ((to + len) > mtd->size)
+	return -EINVAL;
+	if (!len)
+	return 0;
+
+	nand_panic_wait(mtd);
+
+	chip->ops.len = len;
+	chip->ops.datbuf = (uint8_t *)buf;
+	chip->ops.oobbuf = NULL;
+
+	ret = nand_do_write_ops(mtd, to, &chip->ops);
+
+	*retlen = chip->ops.retlen;
+	return ret;
+ }
+

/**
* nand_scan_tail - [NAND Interface] Scan for the NAND device
***************
*** 2879,2884 ****
--- 2917,2923 ----
mtd->write = nand_write;
mtd->read_oob = nand_read_oob;
mtd->write_oob = nand_write_oob;
+	mtd->panic_write = nand_panic_write;
mtd->sync = nand_sync;
mtd->lock = NULL;
mtd->unlock = NULL;
diff -crB linux/drivers/mtd/onenand/Makefile g3/drivers/mtd/onenand/Makefile
*** linux/drivers/mtd/onenand/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/mtd/onenand/Makefile	2011-02-26 04:41:43.000000000 -0800
***************
*** 12,15 ****
# Simulator
obj-$(CONFIG_MTD_ONENAND_SIM)	+= onenand_sim.o

! onenand-objs = onenand_base.o onenand_bbt.o
--- 12,20 ----
# Simulator
obj-$(CONFIG_MTD_ONENAND_SIM)	+= onenand_sim.o

! ifeq ($(CONFIG_CPU_S5P6442),y)
! onenand-objs = s5p6442.o
! else
! onenand-objs = onenand_base.o
! endif
! onenand-objs += onenand_bbt.o
Only in g3/drivers/mtd/onenand: s5p6442.c
[Galaxy 3 Android Development] cdesai:
Difference in drivers/net

diff -crB linux/drivers/net/Kconfig g3/drivers/net/Kconfig
*** linux/drivers/net/Kconfig	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/net/Kconfig	2011-02-26 04:41:43.000000000 -0800
***************
*** 3113,3118 ****
--- 3113,3135 ----
and session setup). One such daemon is OpenL2TP
(http://openl2tp.sourceforge.net/).

+ config PPPOLAC
+	tristate "PPP on L2TP Access Concentrator"
+	depends on PPP && INET
+	help
+	L2TP (RFC 2661) is a tunneling protocol widely used in virtual private
+	networks. This driver handles L2TP data packets between a UDP socket
+	and a PPP channel, but only permits one session per socket. Thus it is
+	fairly simple and suited for clients.
+
+ config PPPOPNS
+	tristate "PPP on PPTP Network Server"
+	depends on PPP && INET
+	help
+	PPTP (RFC 2637) is a tunneling protocol widely used in virtual private
+	networks. This driver handles PPTP data packets between a RAW socket
+	and a PPP channel. It is fairly simple and easy to use.
+
config SLIP
tristate "SLIP (serial line) support"
---help---
diff -crB linux/drivers/net/Makefile g3/drivers/net/Makefile
*** linux/drivers/net/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/net/Makefile	2011-02-26 04:41:43.000000000 -0800
***************
*** 158,163 ****
--- 158,165 ----
obj-$(CONFIG_PPP_MPPE) += ppp_mppe.o
obj-$(CONFIG_PPPOE) += pppox.o pppoe.o
obj-$(CONFIG_PPPOL2TP) += pppox.o pppol2tp.o
+ obj-$(CONFIG_PPPOLAC) += pppox.o pppolac.o
+ obj-$(CONFIG_PPPOPNS) += pppox.o pppopns.o

obj-$(CONFIG_SLIP) += slip.o
obj-$(CONFIG_SLHC) += slhc.o
Only in g3/drivers/net: pppolac.c
Only in g3/drivers/net: pppopns.c
[Galaxy 3 Android Development] cdesai:
Difference in drivers/w1

diff -crB linux/drivers/w1/w1.c g3/drivers/w1/w1.c
*** linux/drivers/w1/w1.c	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/w1/w1.c	2011-02-26 04:41:54.000000000 -0800
***************
*** 517,526 ****
static W1_MASTER_ATTR_RO(attempts, S_IRUGO);
static W1_MASTER_ATTR_RO(timeout, S_IRUGO);
static W1_MASTER_ATTR_RO(pointer, S_IRUGO);
! static W1_MASTER_ATTR_RW(search, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(pullup, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(add, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(remove, S_IRUGO | S_IWUGO);

static struct attribute *w1_master_default_attrs[] = {
&w1_master_attribute_name.attr,
--- 517,526 ----
static W1_MASTER_ATTR_RO(attempts, S_IRUGO);
static W1_MASTER_ATTR_RO(timeout, S_IRUGO);
static W1_MASTER_ATTR_RO(pointer, S_IRUGO);
! static W1_MASTER_ATTR_RW(search, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(pullup, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(add, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(remove, S_IRUGO | S_IWUSR | S_IWGRP);

static struct attribute *w1_master_default_attrs[] = {
&w1_master_attribute_name.attr,
[Galaxy 3 Android Development] cdesai:
Difference in drivers/video

diff -crB linux/drivers/video/fbmem.c g3/drivers/video/fbmem.c
*** linux/drivers/video/fbmem.c	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/video/fbmem.c	2011-02-26 04:41:53.000000000 -0800
***************
*** 1369,1374 ****
--- 1369,1378 ----
return 0;
}

+ #ifdef CONFIG_FB_S3C
+ extern void s3cfb_stop_progress(void);
+ #endif
+
static int
fb_open(struct inode *inode, struct file *file)
__acquires(&info->lock)
***************
*** 1401,1406 ****
--- 1405,1413 ----
if (info->fbdefio)
fb_deferred_io_open(info, inode, file);
#endif
+ #ifdef CONFIG_FB_S3C
+	s3cfb_stop_progress();
+ #endif
out:
mutex_unlock(&info->lock);
return res;
diff -crB linux/drivers/video/Kconfig g3/drivers/video/Kconfig
*** linux/drivers/video/Kconfig	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/video/Kconfig	2011-02-26 04:41:52.000000000 -0800
***************
*** 239,244 ****
--- 239,246 ----
comment "Frame buffer hardware drivers"
depends on FB

+ source "drivers/video/samsung/Kconfig"
+
config FB_CIRRUS
tristate "Cirrus Logic support"
depends on FB && (ZORRO || PCI)
***************
*** 1880,1903 ****
depends on FB_TMIO
default y

- config FB_S3C
-	tristate "Samsung S3C framebuffer support"
-	depends on FB && ARCH_S3C64XX
-	select FB_CFB_FILLRECT
-	select FB_CFB_COPYAREA
-	select FB_CFB_IMAGEBLIT
-	---help---
-	Frame buffer driver for the built-in FB controller in the Samsung
-	SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
-	and the S3C64XX series such as the S3C6400 and S3C6410.
-
-	These chips all have the same basic framebuffer design with the
-	actual capabilities depending on the chip. For instance the S3C6400
-	and S3C6410 support 4 hardware windows whereas the S3C24XX series
-	currently only have two.
-
-	Currently the support is only for the S3C6400 and S3C6410 SoCs.
-
config FB_S3C_DEBUG_REGWRITE
bool "Debug register writes"
depends on FB_S3C
--- 1882,1887 ----
diff -crB linux/drivers/video/Makefile g3/drivers/video/Makefile
*** linux/drivers/video/Makefile	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/video/Makefile	2011-02-26 04:41:52.000000000 -0800
***************
*** 112,119 ****
obj-$(CONFIG_FB_S1D13XXX)	+= s1d13xxxfb.o
obj-$(CONFIG_FB_SH7760)	+= sh7760fb.o
obj-$(CONFIG_FB_IMX) += imxfb.o
- obj-$(CONFIG_FB_S3C)	+= s3c-fb.o
obj-$(CONFIG_FB_S3C2410)	+= s3c2410fb.o
obj-$(CONFIG_FB_FSL_DIU)	+= fsl-diu-fb.o
obj-$(CONFIG_FB_COBALT) += cobalt_lcdfb.o
obj-$(CONFIG_FB_PNX4008_DUM)	+= pnx4008/
--- 112,119 ----
obj-$(CONFIG_FB_S1D13XXX)	+= s1d13xxxfb.o
obj-$(CONFIG_FB_SH7760)	+= sh7760fb.o
obj-$(CONFIG_FB_IMX) += imxfb.o
obj-$(CONFIG_FB_S3C2410)	+= s3c2410fb.o
+ obj-$(CONFIG_FB_S3C)	+= samsung/
obj-$(CONFIG_FB_FSL_DIU)	+= fsl-diu-fb.o
obj-$(CONFIG_FB_COBALT) += cobalt_lcdfb.o
obj-$(CONFIG_FB_PNX4008_DUM)	+= pnx4008/
Only in g3/drivers/video: samsung
[Galaxy 3 Android Development] cdesai:
Difference in drivers/watchdog

diff -crB linux/drivers/w1/w1.c g3/drivers/w1/w1.c
*** linux/drivers/w1/w1.c	2010-02-23 07:38:51.000000000 -0800
--- g3/drivers/w1/w1.c	2011-02-26 04:41:54.000000000 -0800
***************
*** 517,526 ****
static W1_MASTER_ATTR_RO(attempts, S_IRUGO);
static W1_MASTER_ATTR_RO(timeout, S_IRUGO);
static W1_MASTER_ATTR_RO(pointer, S_IRUGO);
! static W1_MASTER_ATTR_RW(search, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(pullup, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(add, S_IRUGO | S_IWUGO);
! static W1_MASTER_ATTR_RW(remove, S_IRUGO | S_IWUGO);

static struct attribute *w1_master_default_attrs[] = {
&w1_master_attribute_name.attr,
--- 517,526 ----
static W1_MASTER_ATTR_RO(attempts, S_IRUGO);
static W1_MASTER_ATTR_RO(timeout, S_IRUGO);
static W1_MASTER_ATTR_RO(pointer, S_IRUGO);
! static W1_MASTER_ATTR_RW(search, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(pullup, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(add, S_IRUGO | S_IWUSR | S_IWGRP);
! static W1_MASTER_ATTR_RW(remove, S_IRUGO | S_IWUSR | S_IWGRP);

static struct attribute *w1_master_default_attrs[] = {
&w1_master_attribute_name.attr,
[Galaxy 3 Android Development] harkan89:
Hahaha.. Good luck mate!
[Galaxy 3 Android Development] Dharam_Maniar:
Update for 31/9/2011:

Ported CPU Driver

Ported Sensors

Update for 1/9/2011:

Ported /drivers/base

Ported /drivers/char

Ported /drivers/cpufreq

Ported /drivers/i2c

Ported /drivers/input

Ported /drivers/leds

Ported /drivers/level

Ported /drivers/media

Ported /drivers/misc

Ported /drivers/mmc

Ported /drivers/modemctl

Ported /drivers/mtd

Ported /drivers/power

Ported /drivers/rtc

marcellusbe also solved a bug which was preventing to compile...

But compiling gives errors as many driver's are still left....

So i will try compiling once after all the required changes are completed...

Hopefully in 2-3 days all the required changes shall be done, and then we can try and compile and see if there are no errors in compiling...

If it compiles properly then maybe we can test the kernel on the device...

Its still risky as it may cause a hardbrick...
[Galaxy 3 Android Development] dhirend_6d:
How would it cause a hardbrick?? You are not touching the bootloader, right??
[Galaxy 3 Android Development] cdesai:
Yes no bootloader mods but

The kernel drivers are still undone

Even the ones that communicate with the usb port and odin

So it can cause a brick

It is not that flashing bootloaders will cause a brick - brick occurs only due to incorrect/corrupt files and/or interrupt in the flashing process

Even a tar made with 7 zip can cause a brick

If there are some other some problems with the port - even the other drivers for e.g. Cpu can cause a brick if improperly implemented
[Galaxy 3 Android Development] djjonastybe:
I believe the most important advantage is battery life and second performance :)

I hope you guys can finish it.
[Galaxy 3 Android Development] raja4sure:
Great news mate........keep on the good work...m sure that u both will succeed ...al d best .
[Galaxy 3 Android Development] brajesh.sharma87:
If its true then its a matter to worry abt. :(
[Galaxy 3 Android Development] Dharam_Maniar:
it is true, only if the .tar contains bootloader files...
[Galaxy 3 Android Development] brajesh.sharma87:
I guessed the same but wasnt confirm so didnt write that.
[Galaxy 3 Android Development] harkan89:
Hey.. Sorry if this is a noobish question.. Just wanted to clarify.. What exactly is the difference between the 2.6.37 kernel you are trying to port and the 2.6.32.9 kernel that already exists on the G3?
[Galaxy 3 Android Development] Dharam_Maniar:
Well, basically it is a newer kernel, so tons of improvements linux did to their base kernel + it will help us use MTD Driver for the NAND device (Marcellusbe can explain better)

and more other features which we can add if this kernel works.
[Galaxy 3 Android Development] harkan89:
So basically.. Better performance.. Right?? Thanks mate :D
[Galaxy 3 Android Development] Dharam_Maniar:
well yes...that is what we are aiming for :)
[Galaxy 3 Android Development] Dharam_Maniar:
Update for 4/9/2011:

Ported /drivers/serial

Ported /drivers/staging

Ported /drivers/storage

Ported /drivers/svnet

Ported /drivers/tfsr

Ported /drivers/usb - :eek:it was a very big one - took me two days:eek:

Ported /drivers/video

Ported /drivers/w1

Ported /drivers/watchdog

So Finally complete /drivers is ported...

https://github.com/dharamg3/2.6.37-Port/commits/master
[Galaxy 3 Android Development] Panos_dm:
Good! What will be the next step? Building?
[Galaxy 3 Android Development] andreapier:
This is great, it's a big step for your project!

Thank you!
[Galaxy 3 Android Development] Dharam_Maniar:
Well there are some more folders left to port in the kernel... Like /include , /sound and maybe some more...

I am going for a picnic tomorrow ;) So mostly i will continue day after tomorrow...

Once all the changes that samsung had done to the 2.6.32.9 kernel are done, we will try to build the kernel and remove the error which come up...

Most probably errors will comeup as many internal funtions of linux kernel have changed , so we will have to see for those functions in 2.6.32.9 and findout their replacement in the 2.6.37.6 CM kernel... :)

Sent from my Galaxy SII
[Galaxy 3 Android Development] Fakirr1:
A simple Q: can we/should we replace the drivers in CM7 ?

I mean: as far as I know, 2D/3D drivers are not complete in CM7 A5Fix1.As much as I understand, U made the drivers (in other, newer kernel) work.Is it compatible with the "older" kernel? Or we/I must wait , until you finish the whole kernel?

(for replace: from CM7 A4 can I get the drivers to A5fix1?.The only thing is missing for me in CM7A5 is the graphic driver.That couse the most of the lags as I see.)

That is why I like to change the drivers..

Thanks for your very hard work( And Marcellusbe too!!) and I hope, that one day, we can use CM7 and CM6.2 fully 'couse of you guys.

Pardon me for bad english
[Galaxy 3 Android Development] Dharam_Maniar:
Well, the drivers in the newer kernel are the same as samsung kernel...

So that wont work...marcellusbe is trying to get the OpenFIMG working with CM7..and I am hopeful he will succeed.. :)
[Galaxy 3 Android Development] dhirend_6d:
Hope he makes it work. If that s done then the main part of CM7 will be done I think. :drool:. :D :):)
[Galaxy 3 Android Development] Dharam_Maniar:
Update for 5/9/2011:

Ported /include

Ported /kernel

Ported /mm

Ported /net

Ported /sound

So all the modifications necessary for Samsung Driver's have been done.

Now is the building of kernel, finding errors and solving them... ;)
[Galaxy 3 Android Development] raja4sure:
half a battle is won. half 2 go............keep on the good work....u both are doing a really good job and very quickly as well.

all d best for rest of the project
[Galaxy 3 Android Development] umangsagar:
Very happy to hear that the hard work by both of you is paying rich dividends now. My wishes for the slog overs :)
[Galaxy 3 Android Development] Darius_AWS:
dharamg3 ! dharamg3 ! dharamg3 ! YOU ARE JUST AWESOME !
[Galaxy 3 Android Development] Dharam_Maniar:
And I am back to work on this kernel port..

as 1.9 of g3mod is done :) :D
[Galaxy 3 Android Development] rickslick:
G8....this kernel should take g3 to a higher level
[Galaxy 3 Android Development] Dharam_Maniar:
The CPU driver compiles properly now...without errors.. :)
[Galaxy 3 Android Development] ilievski.ace:
Nice To hire Theat :)
[Galaxy 3 Android Development] rafadm:
Legolas in one of the movies says :

"They run as if the very whips of their masters were behind them."

I would say

"They work as if the very whips of their masters were behind them."
[Galaxy 3 Android Development] Benjamin_L:
Looking forward to using CM7 with a 2.6.37 kernel :) Thanks all!
[Galaxy 3 Android Development] OrrPenn18:
That is Return of the King :p ;)

and when the Olephaunts arrive :D :D
[Galaxy 3 Android Development] rafadm:
no its not, its from the two towers when legolas aragorn and gmili try to catch up with the urukais that kidnap merry n pipin
[Galaxy 3 Android Development] Dharam_Maniar:
And What if I say, that the following drivers also compile:

char

cpurfreq

s3c-keypad

touchscreen

fimc - camera

g2d

g3d

jpeg

mfc

media/video

mmc

modemctl

onedram

battery
[Galaxy 3 Android Development] Benjamin_L:
Then we say thank you :D
[Galaxy 3 Android Development] Dharam_Maniar:
;)

10char
[Galaxy 3 Android Development] rickslick:
So now whats left?

BTW what % have you completed its seems more than 50% to me
[Galaxy 3 Android Development] Dharam_Maniar:
well we still dont know...how many errors will I face ahead ?

maybe 1-2 errors or maybe 100-200 error :eek: ;) :D
[Galaxy 3 Android Development] rickslick:
I predict the former:) Godspeed
[Galaxy 3 Android Development] harkan89:
Hopefully it'll stay at 1-2 and you can have this up and running soon ;)

Good Luck!:D
[Galaxy 3 Android Development] Dharam_Maniar:
Good try to solve some more errors by Arakmar...

nice work mate :)
[Galaxy 3 Android Development] justchirag:
i was planning to sell of my i5801 and buy i9000.. plans cancelled... :)

not for the developers:

how long before a stable release than i can try.... ppl who following the thread can pl throw some light !! :confused:
[Galaxy 3 Android Development] Dharam_Maniar:
well, there isnt a zImage even for me to try ;)
[Galaxy 3 Android Development] OrrPenn18:
Oops...messed it up ;)
[Galaxy 3 Android Development] hillbeast:
Considering it's still heavily in development and not even in alpha release yet, we'll follow the same rule as CyanogenMod: don't ask for an ETA. We really don't know how long it'll take.

Also note to people that once 2.6.37 is working, G3MOD Team will be working hard on getting it as stable as possible and moving G3MOD over to the new platform so there will be a fair number of people working on making the kernel as good as it can be.
[Galaxy 3 Android Development] dilzo:
Wow the g3mod theam is awesome!!!
[Galaxy 3 Android Development] dhirend_6d:
Status update??
[Galaxy 3 Android Development] cdesai:
http://github.com/dharamg3/2.6.37-port
[Galaxy 3 Android Development] dhirend_6d:
Nice.............!!
[Galaxy 3 Android Development] FadeFx:
Devs, if u face problems you should contact nicademus who successfully ported 2.6.37 and 2.6.38 to the galaxy s (actually he evolved cm7 kernel) and now is even going for 3.0...

----------------------------------------

tapatalked
[Galaxy 3 Android Development] alok1663:
G3 Mod = G3 God