From: Pascal K <pascalkrauth@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Building compat-drivers 3.9-rc4-2 into older Kernel 3.2
Date: Thu, 16 May 2013 10:18:30 +0200 [thread overview]
Message-ID: <CADj18OVBtFzB9yuqWerX1rq4Hj0QMEX4b_AYR9+5p4wNZV26Lw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3381 bytes --]
Hello everybody,
I am trying to build the compat-drivers 3.9-rc4-2 to get a Marvell mwifiex
driver from the later Linux Kernels into my old 3.2 Kernel. I'm running
into some questions, which the PTXdist guru guide and the
AppNote_kernel-driver (seems outdated) documentation doesn't resolve.
I downloaded the compat-drivers (
http:drvbp1.linux-foundation.org/~mcgrof/rel-html/compat-drivers/<http://drvbp1.linux-foundation.org/~mcgrof/rel-html/compat-drivers/>)
to my local_src folder and unzipped it there.
started creating a *.in and make file through
-> ptxdist newpackage linux-src-driver
added the information in the new files created in /rules/ as you can see
in the lines at the bottom of this email. Then I called
-> ptxdist menuconfig
and activated the new menu entry. But now I don't know what else I have to
configure to get the drivers to get compiled into my kernel.
1) Which files do I have to touch next?
2) Why is there a suggestion to add an entry to the menuconfig if I try to
add a newer driver for my kernel?
Thanks in advance,
Pascal
-> compatdriver.in:
## SECTION=project_specific
config COMPATDRIVER
tristate
select KERNEL
prompt "compatdriver"
help
FIXME
-> compatdriver.make
# -*-makefile-*-
#
# Copyright (C) 2013 by <>
#
# See CREDITS for details about who has contributed to this project.
#
# For further information about the PTXdist project and license conditions
# see the README file.
#
#
# We provide this package
#
PACKAGES-$(PTXCONF_COMPATDRIVER) += compatdriver
#
# Paths and names and versions
#
COMPATDRIVER_VERSION := 3.9-rc4-2
COMPATDRIVER := compatdriver-$(COMPATDRIVER_VERSION)
COMPATDRIVER_URL := lndir://$(PTXDIST_WORKSPACE)/local_src/$(COMPATDRIVER)
COMPATDRIVER_DIR := $(BUILDDIR)/$(COMPATDRIVER)
COMPATDRIVER_LICENSE := unknown
ifdef PTXCONF_COMPATDRIVER
$(STATEDIR)/kernel.targetinstall.post:
$(STATEDIR)/compatdriver.targetinstall
endif
#
----------------------------------------------------------------------------
# Prepare
#
----------------------------------------------------------------------------
$(STATEDIR)/compatdriver.prepare:
@$(call targetinfo)
@$(call touch)
#
----------------------------------------------------------------------------
# Compile
#
----------------------------------------------------------------------------
$(STATEDIR)/compatdriver.compile:
@$(call targetinfo)
$(KERNEL_PATH) $(KERNEL_ENV) $(MAKE) $(KERNEL_MAKEVARS) \
-C $(KERNEL_DIR) \
M=$(COMPATDRIVER_DIR) \
modules
@$(call touch)
#
----------------------------------------------------------------------------
# Install
#
----------------------------------------------------------------------------
$(STATEDIR)/compatdriver.install:
@$(call targetinfo)
@$(call touch)
#
----------------------------------------------------------------------------
# Target-Install
#
----------------------------------------------------------------------------
$(STATEDIR)/compatdriver.targetinstall:
@$(call targetinfo)
$(KERNEL_PATH) $(KERNEL_ENV) $(MAKE) $(KERNEL_MAKEVARS) \
-C $(KERNEL_DIR) \
M=$(COMPATDRIVER_DIR) \
modules_install
@$(call touch)
#
----------------------------------------------------------------------------
# Clean
#
----------------------------------------------------------------------------
#$(STATEDIR)/compatdriver.clean:
# @$(call targetinfo)
# @$(call clean_pkg, COMPATDRIVER)
# vim: syntax=make
[-- Attachment #1.2: Type: text/html, Size: 6345 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2013-05-16 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADj18OVBtFzB9yuqWerX1rq4Hj0QMEX4b_AYR9+5p4wNZV26Lw@mail.gmail.com \
--to=pascalkrauth@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox