So we have a portal writer that has written multiple articles on the stuff I made and the stuff we've been doing. He asked us for more info on the Amaze source so he can write about it and help us get more recognition. Don't believe me? Look for yourself.
So can you say what new changes have been made. Did HTC make it harder on us to hack it? Did they not release anything we need? anything so we can get this published. Write it all here and I'll pass the link to this thread to him when we get responses.
Please, only respond here with information on source. NOTHING ELSE! I want to keep it nice and clean here.
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
Devices: Amaze 4g
roms: CyanogenMod 10
Bootloader: Amaze 4G (S-off)
Recovery: 4EXT
I Have ORD
You don't have Dropbox? Sign up here for free
Like my work? Buy Me A Drink(Link above profile pic )
Follow me on Twitter
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
That is one long run on sentence O.o lol. Any other info you guys found out. We need to add more so he can write more about it!
That is one long run on sentence O.o lol. Any other info you guys found out. We need to add more so he can write more about it!
Don't criticize my grammar and writing ability I go to school for that lol but my teachers tell me I'm the best writer in the class
Sent from my HTC_Amaze_4G using xda premium
Devices: Amaze 4g
roms: CyanogenMod 10
Bootloader: Amaze 4G (S-off)
Recovery: 4EXT
I Have ORD
You don't have Dropbox? Sign up here for free
Like my work? Buy Me A Drink(Link above profile pic )
Follow me on Twitter
Wifi is working using the existing modules that HTC provided. Currently we are still looking for a way to get the modules that are compiled by the kernel to work.
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
Quote:
Originally Posted by kozmikkick
Wifi is working using the existing modules that HTC provided. Currently we are still looking for a way to get the modules that are compiled by the kernel to work.
Sent from my HTC One X using xda premium
Yeah, it appears that they commented out the building of the wl12xx drivers, but the stock ICS does have wl12xx modules. The evidence (commentd out makefile, presence of compat.ko, wl12xx.ko, wl12xx_sdio.ko, etc.) points to HTC using a version of compat-wireless drivers, but which one, I don't know. I also don't know if HTC made any modifications to the wireless drivers, but if they did, they'd be obligated by the GPL to release the updates.
Since the tweaks sportsstar used to get wifi work in his kernel worked, that means that we should have everything we need on the kernel side of things, we just need to get and build the proper version of compat wireless. I also wonder if we need to match the version of compat-wireless with the binary firmware blob from TI. In all the work building different versions of compat-wireless, it could be we also need the proper firmware.
Yeah, it appears that they commented out the building of the wl12xx drivers, but the stock ICS does have wl12xx modules. The evidence (commentd out makefile, presence of compat.ko, wl12xx.ko, wl12xx_sdio.ko, etc.) points to HTC using a version of compat-wireless drivers, but which one, I don't know. I also don't know if HTC made any modifications to the wireless drivers, but if they did, they'd be obligated by the GPL to release the updates.
Since the tweaks sportsstar used to get wifi work in his kernel worked, that means that we should have everything we need on the kernel side of things, we just need to get and build the proper version of compat wireless. I also wonder if we need to match the version of compat-wireless with the binary firmware blob from TI. In all the work building different versions of compat-wireless, it could be we also need the proper firmware.
The only problem with the current tweak to use existing wifi modules is that I think it may be breaking other functions. Not sure about this yet though.
When I get my amaze this week my plan is to try a few different firmware from ti. I think you're right about needing to swap out the blobs. If this is the case then it should make things pretty easy.
Ok, since this is a generic thread about ICS source, I'm moving all of my kernel ramblings here, instead of taking up space in Kozmik's kernel thread.
Anyways, I ran modinfo on all the modules in the T-Mobile ICS update. Here are the results:
Code:
filename: bluetooth.ko
alias: net-pf-31
license: GPL
version: 2.16
description: Bluetooth Core ver 2.16
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: 7F6941AC162E74AA0B26DAF
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: disable_esco:Disable eSCO connection creation (bool)
parm: disable_ertm:Disable enhanced retransmission mode (bool)
parm: enable_hs:Enable High Speed (bool)
parm: enable_mgmt:Enable Management interface (bool)
parm: enable_le:Enable LE support (bool)
parm: force_acl_master:Always try to switch to master role on ACL link (int)
filename: bnep.ko
alias: bt-proto-4
license: GPL
version: 1.3
description: Bluetooth BNEP ver 1.3
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: 77A9BE70DF012F020FC7798
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: compress_src:Compress sources headers (bool)
parm: compress_dst:Compress destination headers (bool)
filename: btwilink.ko
license: GPL
version: 1.0
description: Bluetooth Driver for TI Shared Transport1.0
author: Raja Mani <raja_mani@ti.com>
srcversion: 269FE2F6F705EA176E7CD4D
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: cfg80211.ko
description: wireless configuration support
license: GPL
author: Johannes Berg
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: ieee80211_regdom:IEEE 802.11 regulatory domain code (charp)
parm: cfg80211_disable_40mhz_24ghz:Disable 40MHz support in the 2.4GHz band (bool)
filename: compat.ko
license: GPL
description: Kernel compatibility module
author: Luis R. Rodriguez
license: Dual BSD/GPL
author: Broadcom Corporation
description: Cordic functions
license: Dual BSD/GPL
author: Broadcom Corporation
description: CRC8 (by Williams, Ross N.) function
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: compat_base_tree:The upstream tree used as base for this backport (charp)
parm: compat_base_tree_version:The git-describe of the upstream base tree (charp)
parm: compat_version:Version of the kernel compat backport work (charp)
filename: fm_drv.ko
license: GPL
depends:
staging: Y
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: hid-magicmouse.ko
license: GPL
alias: hid:b0005v000005ACp0000030E
alias: hid:b0005v000005ACp0000030D
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: emulate_3button:Emulate a middle button (bool)
parm: emulate_scroll_wheel:Emulate a scroll wheel (bool)
parm: scroll_speed:Scroll speed, value from 0 (slow) to 63 (fast)
parm: scroll_acceleration:Accelerate sequential scroll events (bool)
parm: report_touches:Emit touch records (otherwise, only use them for emulation) (bool)
parm: report_undeciphered:Report undeciphered multi-touch state field using a MSC_RAW event (bool)
filename: hidp.ko
alias: bt-proto-6
license: GPL
version: 1.2
description: Bluetooth HIDP ver 1.2
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: AC3509329E41D74FA70B7C0
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: mac80211.ko
license: GPL
description: IEEE 802.11 subsystem
depends: cfg80211
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: ieee80211_default_rc_algo:Default rate control algorithm for mac80211 to use (charp)
parm: max_nullfunc_tries:Maximum nullfunc tx tries before disconnecting (reason 4). (int)
parm: max_probe_tries:Maximum probe tries before disconnecting (reason 4). (int)
parm: probe_wait_ms:Maximum time(ms) to wait for probe response before disconnecting (reason 4). (int)
filename: rfcomm.ko
alias: bt-proto-3
license: GPL
version: 1.11
description: Bluetooth RFCOMM ver 1.11
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: 436C8832D80BAD759212601
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: disable_cfc:Disable credit based flow control (bool)
parm: channel_mtu:Default MTU for the RFCOMM channel (int)
parm: l2cap_mtu:Default MTU for the L2CAP connection (uint)
parm: l2cap_ertm:Use L2CAP ERTM mode for connection (bool)
filename: wl12xx.ko
author: Juuso Oikarinen <juuso.oikarinen@nokia.com>
author: Luciano Coelho <coelho@ti.com>
license: GPL
alias: platform:wl12xx
depends: cfg80211,mac80211
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: debug_level:wl12xx debugging level (uint)
parm: fwlog:charp
parm: keymap:FW logger options: continuous, ondemand, dbgpins or disable
parm: bug_on_recovery:BUG() on fw recovery (bool)
parm: fref:FREF clock: 19.2, 26, 26x, 38.4, 38.4x, 52 (charp)
parm: tcxo:TCXO clock: 19.2, 26, 38.4, 52, 16.368, 32.736, 16.8, 33.6 (charp)
filename: wl12xx_sdio.ko
firmware: ti-connectivity/wl128x-fw-4-mr.bin
firmware: ti-connectivity/wl128x-fw-4-sr.bin
firmware: ti-connectivity/wl127x-fw-4-mr.bin
firmware: ti-connectivity/wl127x-fw-4-sr.bin
author: Juuso Oikarinen <juuso.oikarinen@nokia.com>
author: Luciano Coelho <coelho@ti.com>
license: GPL
alias: sdio:c*v0097d4076*
depends: wl12xx
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
They are all GPL with the exception of compat.ko being dual licensed. I don't think that should be an issue (ie. doubt HTC had modifications) as I think that modules function is to interface with the other drivers (wl12xx, etc.) to the current kernel version. The rest are GPL and therefore HTC must release the source for it.
They are all GPL with the exception of compat.ko being dual licensed.
I'm not perfectly clear on dual licenses, so it should be posed to FSF, but from what I understand, it allows the code to be compatible with GPL and BSD projects. However, if used in a GPL project, I believe the GPL portion of the license is what takes effect, since the BSD portion is not compatible with the GPL project.
A quote from Linus Torvalds:
Quote:
"This is no different from the fact that we have some drivers that are GPLv2/BSD licensed. Within the kernel, they are GPLv2. But on their own, you can choose to use them under the BSD license, make your changes to them, and release them commercially. And correct - I cannot (and neither can anybody else) then accept those *non*GPLv2 changes back."
I'm having trouble with "on their own" and "within the kernel".
New Mobile Operating System Jolla Sailfish‘s … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?