<pyongyang>
I've been farting around with the Y300 kernel
<codename13>
What did you manage to do?
<pyongyang>
Get drivedroid to report as a CD-ROM
<pyongyang>
It's been reporting a USB HDD.
<pyongyang>
Which doesn't let you exploit the boot options menu
<codename13>
That's sound too complex for my simple mind ._.
<pyongyang>
nag, you're doing good.
<pyongyang>
nah even
<codename13>
I don't know what to do to fix my problems up above
<codename13>
If you can't seem them, look at the end of the IRC log for the 26th (yesterday)
<pyongyang>
have you messed with devices-msm7x27a.c?
<codename13>
Sort of, but not really. I'm afraid I'll break something crucial.
<pyongyang>
What do you mean, sort of?
<pyongyang>
That's a yes or no question
<codename13>
I've tried mixing and matching code from the devices-msm7x27a.c from my original kernel
<codename13>
I've done "light messing" with it
<pyongyang>
Revert back to the version that came with your kernel
<codename13>
The version that came with the kernel I'm porting or my stock kernel?
<pyongyang>
the version that came with stock
<codename13>
I compiled the kernel I'm trying to port for generic msm7x27a and I didn't get any errors with devices-msm7x27a, so maybe it's a board file issue with my device's board file?
<pyongyang>
tbh, I'd suspect you've missed a brace or something daft like that, without researching it
<pyongyang>
I'd leave the board specific stuff alone, though.
<pyongyang>
Assuming that's possible.
<codename13>
I replaced the devices-msm7x27a.c with the one from my stock kernel, now here are the errors: http://pastebin.com/vCdJpLm4
<pyongyang>
Make you made clean?
<pyongyang>
Have you even
<codename13>
Yes, just made clean and retried making. Same errors :/
* pyongyang
sighs
<codename13>
any idea what to do?
<codename13>
Maybe the headers are messed up?
<codename13>
But why would it compile normally when built with the generic msm7627a defconfig?]
<pyongyang>
#ifdef
<pyongyang>
Gives you conditional compilation
<codename13>
I fixed it sort of
<pyongyang>
:)
<codename13>
devices-msm7627a.c compiles
<pyongyang>
won't link?
<codename13>
I looked in the msm7627a defconfig and saw CONFIG_ARCH_MSM8625=y
<codename13>
I copied enabled it in my device's defconfig as well and devices-msm7x27a.c compiled (I compiled the one from the port kernel too)
pyongyang has quit [Remote host closed the connection]
luca020400 has joined #huawei-g300
rhen_ has quit [Quit: Leaving]
gregor160300 has joined #huawei-g300
<lithiumpt>
anyone?
<lithiumpt>
why do almost all android devices have such a small internal storage? :((
<Shadowghoster>
jvb yes there is CM12 and SlimLP
<lithiumpt>
by internal storage i mean actual app installation location
<Shadowghoster>
lithiumpt it's because more than 4gb internal can cost money while importing to some countries
<lithiumpt>
why don't the single partition it?
<lithiumpt>
why the separation between the internal storage and internal sd card...
<luca020400>
huawei choice
<lithiumpt>
the=they
<Shadowghoster>
jup
<luca020400>
in newer phone usually they use /data as insternal storage
* Shadowghoster
has now 3 weeks of chilling ^^
<luca020400>
/data/media
<lithiumpt>
just bought an unbranded tablet with 16gb
<lithiumpt>
only 1gb of actually internal storage
<lithiumpt>
is there a generic way to work around this?
<lithiumpt>
changing mount points or something
<lithiumpt>
i guess i'll just return it..
<luca020400>
I love cm12.1
<luca020400>
If I use 1st slim slot systemui crash
<luca020400>
if I use 2nd one it works
<luca020400>
xd
<luca020400>
*sim slot
gregor160300 has quit [Read error: Connection reset by peer]
chil360 has quit [Quit: Konversation terminated!]
Solitary has joined #huawei-g300
Shadowghoster is now known as Ghost|afk
Ghost|afk is now known as Shadowghoster
luca020400 has quit [Remote host closed the connection]
luca020400 has joined #huawei-g300
<codename13>
CC net/bluetooth/mgmt.o In file included from include/linux/cgroup.h:11:0, from include/net/netprio_cgroup.h:16, from include/linux/netdevice.h:54, from include/net/sock.h:50, from include/net/bluetooth/bluetooth.h:32, from net/bluetooth/mgmt.c:29: include/linux/sched.h:2978:37: warning: "CONFIG_TASK_DELAY_ACCT" is not defined [-Wundef
<codename13>
CC net/bluetooth/mgmt.o In file included from include/linux/cgroup.h:11:0, from include/net/netprio_cgroup.h:16, from include/linux/netdevice.h:54, from include/net/sock.h:50, from include/net/bluetooth/bluetooth.h:32, from net/bluetooth/mgmt.c:29: include/linux/sched.h:2978:37: warning: "CONFIG_TASK_DELAY_ACCT" is not defined [-Wundef
<codename13>
Sorry, anyone know how to fix this:
<codename13>
include/net/bluetooth/hci_core.h:209:24: error: field 'cmd_task' has incomplete type
<codename13>
include/net/bluetooth/hci_core.h:210:24: error: field 'rx_task' has incomplete type
<luca020400>
Hmm
<codename13>
include/net/bluetooth/hci_core.h:211:24: error: field 'tx_task' has incomplete type
<luca020400>
Source code xd
<codename13>
I've played around with the bluetooth drivers and I don't know how to fix this error
<luca020400>
A y300
<luca020400>
Anyway I will not look in it xd . I'm at bed