Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

silead_ts has to be disabled, and that makes distributions unhappy #3

Open
ssinyagin opened this issue Mar 14, 2017 · 1 comment
Open

Comments

@ssinyagin
Copy link

In order to make use of gslx680_ts_acpi module, the original upstream module silead_ts has to be disabled. The kernel build script of Ubuntu is unhappy about a module that disappears. Is there a way to keep the old module too?

There is a way to put the old module into ignore list, if it's totally outdated. Is it completely useless?

@hopkinskong
Copy link
Owner

There are few ways, though they are not the best idea.

  1. Remove the entry in Makefile for the silead_ts config, and remove my added dependencies on gslx680_ts_acpi on Kconfig. You can now say Y on both driver, but due to removed Makefile entry, silead_ts will not build.
  2. Completely replace the gslx680_ts_acpi to silead_ts. This is the most straightforward idea, but I don't want to remove anything from the base kernel, that's why I didn't do it as I rather disable it.
  3. Don't use Ubuntu build script (Seems not an option for you)

Btw, what do you mean Ubuntu is unhappy about a module that disappears, do you mean just putting N on the silead_ts will have the kernel failed to build?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants