2003-10-17 15:40:02 +07:00
|
|
|
# Makefile for udev
|
2005-04-27 10:59:47 +07:00
|
|
|
#
|
2003-10-17 15:40:02 +07:00
|
|
|
# Copyright (C) 2003 Greg Kroah-Hartman <greg@kroah.com>
|
2005-04-27 10:59:47 +07:00
|
|
|
#
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
|
|
# it under the terms of the GNU General Public License as published by
|
|
|
|
# the Free Software Foundation; version 2 of the License.
|
|
|
|
#
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
# General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program; if not, write to the Free Software
|
|
|
|
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
|
|
|
#
|
|
|
|
|
[PATCH] add udev logging to info log
On Thu, Jan 15, 2004 at 05:14:16AM +0100, Kay Sievers wrote:
> On Wed, Jan 14, 2004 at 01:10:43PM -0800, Greg KH wrote:
> > On Wed, Jan 14, 2004 at 02:34:26PM -0600, Clay Haapala wrote:
> > > On Wed, 14 Jan 2004, Chris Friesen spake thusly:
> > > >
> > > > Maybe for ones with a matching rule, you could print something like:
> > > >
> > > >
> > > Is the act of printing/syslogging a rule in an of itself?
> >
> > No, as currently the only way stuff ends up in the syslog is if
> > DEBUG=true is used on the build line.
> >
> > But it's sounding like we might want to change that... :)
>
> How about this in the syslog after connect/disconnect?
>
> Jan 15 05:07:45 pim udev[28007]: configured rule in '/etc/udev/udev.rules' at line 17 applied, 'video*' becomes 'video/webcam%n'
> Jan 15 05:07:45 pim udev[28007]: creating device node '/udev/video/webcam0'
> Jan 15 05:07:47 pim udev[28015]: removing device node '/udev/video/webcam0'
Here is a slightly better version. I've created a logging.h file and
moved the debug macros from udev.h in there.
If you type:
'make' - you will get a binary that prints one or two lines to syslog
if a device node is created or deleted
'make LOG=false' - you get a binary that prints asolutely nothing
'make DEBUG=true' - the same as today, it will print all debug lines
2004-01-16 12:53:20 +07:00
|
|
|
# Set the following to control the use of syslog
|
|
|
|
# Set it to `false' to remove all logging
|
|
|
|
LOG = true
|
|
|
|
|
|
|
|
# Set the following to `true' to log the debug
|
|
|
|
# and make a unstripped, unoptimized binary.
|
2005-04-27 10:59:47 +07:00
|
|
|
# Leave this set to `false' for production use.
|
2003-12-03 09:41:29 +07:00
|
|
|
DEBUG = false
|
2005-04-27 10:59:47 +07:00
|
|
|
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
# Set the following to `true' to make udev emit a D-BUS signal when a
|
|
|
|
# new node is created.
|
2003-12-17 14:41:59 +07:00
|
|
|
USE_DBUS = false
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
ROOT = udev
|
2004-01-15 09:16:32 +07:00
|
|
|
VERSION = 013_bk
|
2005-04-27 10:59:47 +07:00
|
|
|
INSTALL_DIR = /usr/local/bin
|
2003-04-11 01:25:55 +07:00
|
|
|
RELEASE_NAME = $(ROOT)-$(VERSION)
|
2004-01-01 11:35:02 +07:00
|
|
|
LOCAL_CFG_DIR = etc/udev
|
2005-04-27 10:59:47 +07:00
|
|
|
|
2003-10-30 13:26:35 +07:00
|
|
|
DESTDIR =
|
2003-10-16 13:50:13 +07:00
|
|
|
# override this to make udev look in a different location for it's config files
|
2003-10-17 11:18:40 +07:00
|
|
|
prefix =
|
|
|
|
exec_prefix = ${prefix}
|
|
|
|
etcdir = ${prefix}/etc
|
|
|
|
sbindir = ${exec_prefix}/sbin
|
|
|
|
mandir = ${prefix}/usr/share/man
|
|
|
|
hotplugdir = ${etcdir}/hotplug.d/default
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
dbusdir = ${etcdir}/dbus-1/system.d
|
2003-10-17 11:18:40 +07:00
|
|
|
configdir = ${etcdir}/udev/
|
2003-12-16 13:22:34 +07:00
|
|
|
initdir = ${etcdir}/init.d/
|
2003-10-17 11:18:40 +07:00
|
|
|
srcdir = .
|
|
|
|
|
|
|
|
INSTALL = /usr/bin/install -c
|
|
|
|
INSTALL_PROGRAM = ${INSTALL}
|
|
|
|
INSTALL_DATA = ${INSTALL} -m 644
|
|
|
|
INSTALL_SCRIPT = ${INSTALL_PROGRAM}
|
|
|
|
|
2003-12-08 00:04:49 +07:00
|
|
|
# To build any of the extras programs, run with:
|
|
|
|
# make EXTRAS="extras/a extras/b"
|
|
|
|
EXTRAS=
|
2003-10-16 13:50:13 +07:00
|
|
|
|
|
|
|
# place to put our device nodes
|
2003-12-11 23:00:40 +07:00
|
|
|
udevdir = ${prefix}/udev
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
# Comment out this line to build with something other
|
|
|
|
# than the local version of klibc
|
2003-12-17 14:41:59 +07:00
|
|
|
#USE_KLIBC = true
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
# If you are running a cross compiler, you may want to set this
|
2004-01-10 16:19:57 +07:00
|
|
|
# to something more interesting, like "arm-linux-". If you want
|
2005-04-27 10:59:47 +07:00
|
|
|
# to compile vs uClibc, that can be done here as well.
|
|
|
|
CROSS = #/usr/i386-linux-uclibc/usr/bin/i386-uclibc-
|
|
|
|
CC = $(CROSS)gcc
|
2003-11-25 13:10:23 +07:00
|
|
|
LD = $(CROSS)gcc
|
2005-04-27 10:59:47 +07:00
|
|
|
AR = $(CROSS)ar
|
|
|
|
STRIP = $(CROSS)strip
|
2003-08-05 15:10:01 +07:00
|
|
|
RANLIB = $(CROSS)ranlib
|
2005-04-27 10:59:47 +07:00
|
|
|
|
2003-12-08 00:04:49 +07:00
|
|
|
export CROSS CC AR STRIP RANLIB CFLAGS LDFLAGS LIB_OBJS ARCH_LIB_OBJS CRT0
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
# code taken from uClibc to determine the current arch
|
|
|
|
ARCH := ${shell $(CC) -dumpmachine | sed -e s'/-.*//' -e 's/i.86/i386/' -e 's/sparc.*/sparc/' \
|
2003-12-02 15:44:48 +07:00
|
|
|
-e 's/arm.*/arm/g' -e 's/m68k.*/m68k/' -e 's/powerpc/ppc/g'}
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
# code taken from uClibc to determine the gcc include dir
|
|
|
|
GCCINCDIR := ${shell $(CC) -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp"}
|
|
|
|
|
|
|
|
# code taken from uClibc to determine the libgcc.a filename
|
|
|
|
GCC_LIB := $(shell $(CC) -print-libgcc-file-name )
|
|
|
|
|
|
|
|
# use '-Os' optimization if available, else use -O2
|
|
|
|
OPTIMIZATION := ${shell if $(CC) -Os -S -o /dev/null -xc /dev/null >/dev/null 2>&1; \
|
|
|
|
then echo "-Os"; else echo "-O2" ; fi}
|
|
|
|
|
2003-10-22 14:18:49 +07:00
|
|
|
# add -Wredundant-decls when libsysfs gets cleaned up
|
|
|
|
WARNINGS := -Wall -Wshadow -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
# Some nice architecture specific optimizations
|
|
|
|
ifeq ($(strip $(TARGET_ARCH)),arm)
|
|
|
|
OPTIMIZATION+=-fstrict-aliasing
|
|
|
|
endif
|
|
|
|
ifeq ($(strip $(TARGET_ARCH)),i386)
|
|
|
|
OPTIMIZATION+=-march=i386
|
|
|
|
OPTIMIZATION += ${shell if $(CC) -mpreferred-stack-boundary=2 -S -o /dev/null -xc \
|
|
|
|
/dev/null >/dev/null 2>&1; then echo "-mpreferred-stack-boundary=2"; fi}
|
|
|
|
OPTIMIZATION += ${shell if $(CC) -malign-functions=0 -malign-jumps=0 -S -o /dev/null -xc \
|
|
|
|
/dev/null >/dev/null 2>&1; then echo "-malign-functions=0 -malign-jumps=0"; fi}
|
|
|
|
CFLAGS+=-pipe
|
|
|
|
else
|
|
|
|
CFLAGS+=-pipe
|
|
|
|
endif
|
|
|
|
|
[PATCH] add udev logging to info log
On Thu, Jan 15, 2004 at 05:14:16AM +0100, Kay Sievers wrote:
> On Wed, Jan 14, 2004 at 01:10:43PM -0800, Greg KH wrote:
> > On Wed, Jan 14, 2004 at 02:34:26PM -0600, Clay Haapala wrote:
> > > On Wed, 14 Jan 2004, Chris Friesen spake thusly:
> > > >
> > > > Maybe for ones with a matching rule, you could print something like:
> > > >
> > > >
> > > Is the act of printing/syslogging a rule in an of itself?
> >
> > No, as currently the only way stuff ends up in the syslog is if
> > DEBUG=true is used on the build line.
> >
> > But it's sounding like we might want to change that... :)
>
> How about this in the syslog after connect/disconnect?
>
> Jan 15 05:07:45 pim udev[28007]: configured rule in '/etc/udev/udev.rules' at line 17 applied, 'video*' becomes 'video/webcam%n'
> Jan 15 05:07:45 pim udev[28007]: creating device node '/udev/video/webcam0'
> Jan 15 05:07:47 pim udev[28015]: removing device node '/udev/video/webcam0'
Here is a slightly better version. I've created a logging.h file and
moved the debug macros from udev.h in there.
If you type:
'make' - you will get a binary that prints one or two lines to syslog
if a device node is created or deleted
'make LOG=false' - you get a binary that prints asolutely nothing
'make DEBUG=true' - the same as today, it will print all debug lines
2004-01-16 12:53:20 +07:00
|
|
|
ifeq ($(strip $(LOG)),true)
|
|
|
|
CFLAGS += -DLOG
|
|
|
|
endif
|
|
|
|
|
2005-04-27 10:59:47 +07:00
|
|
|
# if DEBUG is enabled, then we do not strip or optimize
|
|
|
|
ifeq ($(strip $(DEBUG)),true)
|
|
|
|
CFLAGS += $(WARNINGS) -O1 -g -DDEBUG -D_GNU_SOURCE
|
|
|
|
LDFLAGS += -Wl,-warn-common
|
|
|
|
STRIPCMD = /bin/true -Since_we_are_debugging
|
|
|
|
else
|
|
|
|
CFLAGS += $(WARNINGS) $(OPTIMIZATION) -fomit-frame-pointer -D_GNU_SOURCE
|
|
|
|
LDFLAGS += -s -Wl,-warn-common
|
|
|
|
STRIPCMD = $(STRIP) -s --remove-section=.note --remove-section=.comment
|
|
|
|
endif
|
|
|
|
|
2004-01-01 10:11:04 +07:00
|
|
|
# If we are using our version of klibc, then we need to build, link it, and then
|
|
|
|
# link udev against it statically.
|
|
|
|
# Otherwise, use glibc and link dynamically.
|
2003-12-17 14:41:59 +07:00
|
|
|
ifeq ($(strip $(USE_KLIBC)),true)
|
2003-12-08 00:04:49 +07:00
|
|
|
KLIBC_BASE = $(PWD)/klibc
|
|
|
|
KLIBC_DIR = $(KLIBC_BASE)/klibc
|
2005-04-27 10:59:47 +07:00
|
|
|
INCLUDE_DIR := $(KLIBC_DIR)/include
|
2003-12-08 00:04:49 +07:00
|
|
|
LINUX_INCLUDE_DIR := $(KLIBC_BASE)/linux/include
|
2003-11-25 13:10:23 +07:00
|
|
|
include $(KLIBC_DIR)/arch/$(ARCH)/MCONFIG
|
2005-04-27 10:59:47 +07:00
|
|
|
# arch specific objects
|
|
|
|
ARCH_LIB_OBJS = \
|
2003-12-08 00:04:49 +07:00
|
|
|
$(KLIBC_DIR)/libc.a
|
2005-04-27 10:59:47 +07:00
|
|
|
|
|
|
|
|
2003-10-25 14:21:18 +07:00
|
|
|
CRT0 = $(KLIBC_DIR)/crt0.o
|
2003-11-25 13:10:23 +07:00
|
|
|
LIBC = $(ARCH_LIB_OBJS) $(LIB_OBJS) $(CRT0)
|
|
|
|
CFLAGS += -nostdinc -I$(INCLUDE_DIR) -I$(KLIBC_DIR)/arch/$(ARCH)/include \
|
2003-12-08 00:04:49 +07:00
|
|
|
-I$(INCLUDE_DIR)/bits$(BITSIZE) -I$(GCCINCDIR) -I$(LINUX_INCLUDE_DIR) \
|
[PATCH] fix klibc with printf() and gcc
On Mon, Jan 12, 2004 at 05:04:45PM -0800, Greg KH wrote:
> Very nice, applied. But I did have to make one small change to get the
> code to build properly with klibc:
>
> > +static void print_record(char *path, struct udevice *dev)
> > +{
> > + printf("P: %s\n", path);
> > + printf("N: %s\n", dev->name);
> > + printf("S: %s\n", dev->symlink);
> > + printf("O: %s\n", dev->owner);
> > + printf("G: %s\n", dev->group);
> > + printf("\n");
> > +}
>
> Turns out that gcc likes to convert single character printf() calls to
> putchar() which is only defined in klibc as a macro :(
Just for information. This seems to fix the gcc with klibc :)
2004-01-14 09:48:33 +07:00
|
|
|
-D__KLIBC__ -fno-builtin-printf
|
2003-10-25 14:21:18 +07:00
|
|
|
LIB_OBJS =
|
2003-12-02 15:59:36 +07:00
|
|
|
LDFLAGS = --static --nostdlib -nostartfiles -nodefaultlibs
|
2005-04-27 10:59:47 +07:00
|
|
|
else
|
2003-10-25 14:21:18 +07:00
|
|
|
CRT0 =
|
2005-04-27 10:59:47 +07:00
|
|
|
LIBC =
|
|
|
|
CFLAGS += -I$(GCCINCDIR)
|
|
|
|
LIB_OBJS = -lc
|
2004-01-01 10:11:04 +07:00
|
|
|
LDFLAGS =
|
2005-04-27 10:59:47 +07:00
|
|
|
endif
|
|
|
|
|
2003-12-08 00:04:49 +07:00
|
|
|
CFLAGS += -I$(PWD)/libsysfs
|
|
|
|
|
2003-12-02 14:50:09 +07:00
|
|
|
all: $(ROOT)
|
2003-12-18 09:32:53 +07:00
|
|
|
@extras="$(EXTRAS)" ; for target in $$extras ; do \
|
2003-12-08 00:04:49 +07:00
|
|
|
echo $$target ; \
|
|
|
|
$(MAKE) prefix=$(prefix) LD="$(LD)" SYSFS="$(SYSFS)" \
|
|
|
|
-C $$target $@ ; \
|
|
|
|
done ; \
|
2005-04-27 10:59:47 +07:00
|
|
|
|
2003-12-02 14:50:09 +07:00
|
|
|
$(ROOT): $(LIBC)
|
|
|
|
|
|
|
|
$(ARCH_LIB_OBJS) : $(CRT0)
|
|
|
|
|
|
|
|
$(CRT0):
|
2005-04-27 10:59:47 +07:00
|
|
|
$(MAKE) -C klibc
|
|
|
|
|
2003-10-23 09:40:52 +07:00
|
|
|
TDB = tdb/tdb.o \
|
|
|
|
tdb/spinlock.o
|
|
|
|
|
2003-12-08 00:04:49 +07:00
|
|
|
SYSFS = $(PWD)/libsysfs/sysfs_bus.o \
|
|
|
|
$(PWD)/libsysfs/sysfs_class.o \
|
|
|
|
$(PWD)/libsysfs/sysfs_device.o \
|
|
|
|
$(PWD)/libsysfs/sysfs_dir.o \
|
|
|
|
$(PWD)/libsysfs/sysfs_driver.o \
|
|
|
|
$(PWD)/libsysfs/sysfs_utils.o \
|
|
|
|
$(PWD)/libsysfs/dlist.o
|
2003-08-06 14:03:30 +07:00
|
|
|
|
2005-04-27 10:59:47 +07:00
|
|
|
OBJS = udev.o \
|
2003-12-03 16:08:46 +07:00
|
|
|
udev_config.o \
|
2003-07-21 10:48:48 +07:00
|
|
|
udev-add.o \
|
|
|
|
udev-remove.o \
|
2003-08-06 14:03:30 +07:00
|
|
|
udevdb.o \
|
2003-07-17 15:24:51 +07:00
|
|
|
logging.o \
|
2003-08-06 14:03:30 +07:00
|
|
|
namedev.o \
|
2003-12-03 09:38:30 +07:00
|
|
|
namedev_parse.o \
|
2003-10-23 09:40:52 +07:00
|
|
|
$(SYSFS) \
|
2003-08-06 14:03:30 +07:00
|
|
|
$(TDB)
|
2003-07-19 12:43:45 +07:00
|
|
|
|
2003-12-17 14:41:59 +07:00
|
|
|
ifeq ($(strip $(USE_KLIBC)),true)
|
2003-11-24 11:56:52 +07:00
|
|
|
OBJS += klibc_fixups.o
|
|
|
|
endif
|
|
|
|
|
2003-12-17 14:41:59 +07:00
|
|
|
ifeq ($(USE_DBUS), true)
|
2003-12-09 09:01:56 +07:00
|
|
|
CFLAGS += -DUSE_DBUS
|
|
|
|
CFLAGS += $(shell pkg-config --cflags dbus-1)
|
2003-12-10 16:02:03 +07:00
|
|
|
LDFLAGS += $(shell pkg-config --libs dbus-1)
|
2003-12-09 09:01:56 +07:00
|
|
|
OBJS += udev_dbus.o
|
|
|
|
endif
|
|
|
|
|
2005-04-27 10:59:47 +07:00
|
|
|
# header files automatically generated
|
|
|
|
GEN_HEADERS = udev_version.h
|
|
|
|
|
|
|
|
# Rules on how to create the generated header files
|
|
|
|
udev_version.h:
|
2003-10-16 13:50:13 +07:00
|
|
|
@echo \#define UDEV_VERSION \"$(VERSION)\" > $@
|
2003-12-11 23:00:40 +07:00
|
|
|
@echo \#define UDEV_ROOT \"$(udevdir)/\" >> $@
|
|
|
|
@echo \#define UDEV_DB \"$(udevdir)/\.udev.tdb\" >> $@
|
2003-12-03 23:13:11 +07:00
|
|
|
@echo \#define UDEV_CONFIG_DIR \"$(configdir)\" >> $@
|
|
|
|
@echo \#define UDEV_CONFIG_FILE \"$(configdir)\udev.conf\" >> $@
|
|
|
|
@echo \#define UDEV_RULES_FILE \"$(configdir)\udev.rules\" >> $@
|
|
|
|
@echo \#define UDEV_PERMISSION_FILE \"$(configdir)\udev.permissions\" >> $@
|
2005-04-27 10:59:47 +07:00
|
|
|
|
2003-12-11 23:12:29 +07:00
|
|
|
# config files automatically generated
|
2004-01-01 11:35:02 +07:00
|
|
|
GEN_CONFIGS = $(LOCAL_CFG_DIR)/udev.conf
|
2003-12-11 23:12:29 +07:00
|
|
|
|
|
|
|
# Rules on how to create the generated config files
|
2004-01-01 11:35:02 +07:00
|
|
|
$(LOCAL_CFG_DIR)/udev.conf:
|
|
|
|
sed -e "s:@udevdir@:$(udevdir):" < $(LOCAL_CFG_DIR)/udev.conf.in > $@
|
2003-12-11 23:12:29 +07:00
|
|
|
|
|
|
|
|
2003-12-02 14:50:09 +07:00
|
|
|
$(OBJS): $(GEN_HEADERS)
|
2005-04-27 10:59:47 +07:00
|
|
|
|
[PATCH] add udev logging to info log
On Thu, Jan 15, 2004 at 05:14:16AM +0100, Kay Sievers wrote:
> On Wed, Jan 14, 2004 at 01:10:43PM -0800, Greg KH wrote:
> > On Wed, Jan 14, 2004 at 02:34:26PM -0600, Clay Haapala wrote:
> > > On Wed, 14 Jan 2004, Chris Friesen spake thusly:
> > > >
> > > > Maybe for ones with a matching rule, you could print something like:
> > > >
> > > >
> > > Is the act of printing/syslogging a rule in an of itself?
> >
> > No, as currently the only way stuff ends up in the syslog is if
> > DEBUG=true is used on the build line.
> >
> > But it's sounding like we might want to change that... :)
>
> How about this in the syslog after connect/disconnect?
>
> Jan 15 05:07:45 pim udev[28007]: configured rule in '/etc/udev/udev.rules' at line 17 applied, 'video*' becomes 'video/webcam%n'
> Jan 15 05:07:45 pim udev[28007]: creating device node '/udev/video/webcam0'
> Jan 15 05:07:47 pim udev[28015]: removing device node '/udev/video/webcam0'
Here is a slightly better version. I've created a logging.h file and
moved the debug macros from udev.h in there.
If you type:
'make' - you will get a binary that prints one or two lines to syslog
if a device node is created or deleted
'make LOG=false' - you get a binary that prints asolutely nothing
'make DEBUG=true' - the same as today, it will print all debug lines
2004-01-16 12:53:20 +07:00
|
|
|
$(ROOT): $(OBJS) udev.h namedev.h udev_version.h udev_dbus.h udevdb.h klibc_fixups.h logging.h list.h
|
2003-11-25 13:10:23 +07:00
|
|
|
$(LD) $(LDFLAGS) -o $(ROOT) $(CRT0) $(OBJS) $(LIB_OBJS) $(ARCH_LIB_OBJS)
|
2005-04-27 10:59:47 +07:00
|
|
|
$(STRIPCMD) $(ROOT)
|
|
|
|
|
|
|
|
clean:
|
|
|
|
-find . \( -not -type d \) -and \( -name '*~' -o -name '*.[oas]' \) -type f -print \
|
|
|
|
| xargs rm -f
|
2003-12-11 23:12:29 +07:00
|
|
|
-rm -f core $(ROOT) $(GEN_HEADERS) $(GEN_CONFIGS)
|
2005-04-27 10:59:47 +07:00
|
|
|
$(MAKE) -C klibc clean
|
2003-12-18 09:32:53 +07:00
|
|
|
@extras="$(EXTRAS)" ; for target in $$extras ; do \
|
2003-12-08 00:04:49 +07:00
|
|
|
echo $$target ; \
|
|
|
|
$(MAKE) prefix=$(prefix) LD="$(LD)" SYSFS="$(SYSFS)" \
|
|
|
|
-C $$target $@ ; \
|
|
|
|
done ; \
|
2005-04-27 10:59:47 +07:00
|
|
|
|
2004-01-10 16:19:57 +07:00
|
|
|
DISTFILES = $(shell find . \( -not -name '.' \) -print | grep -v -e CVS -e "\.tar\.gz$" -e "\/\." -e releases -e BitKeeper -e SCCS -e "\.tdb$" -e test/sys | sort )
|
2005-04-27 10:59:47 +07:00
|
|
|
DISTDIR := $(RELEASE_NAME)
|
|
|
|
srcdir = .
|
2003-11-19 12:35:44 +07:00
|
|
|
release: clean
|
|
|
|
@echo "--------------------------cut here------------------------"
|
|
|
|
@echo "cd .."
|
|
|
|
@echo "rm -rf $(DISTDIR)"
|
|
|
|
@echo "mkdir $(DISTDIR)"
|
|
|
|
@echo "chmod 777 $(DISTDIR)"
|
|
|
|
@echo "cp -avr udev/* $(DISTDIR)"
|
|
|
|
@echo "tar -c $(DISTDIR) | gzip -9 > $(RELEASE_NAME).tar.gz"
|
|
|
|
@echo "rm -rf $(DISTDIR)"
|
|
|
|
@echo "--------------------------cut here------------------------"
|
|
|
|
|
|
|
|
|
|
|
|
small_release: $(DISTFILES) clean
|
2005-04-27 10:59:47 +07:00
|
|
|
# @echo $(DISTFILES)
|
|
|
|
@-rm -rf $(DISTDIR)
|
|
|
|
@mkdir $(DISTDIR)
|
|
|
|
@-chmod 777 $(DISTDIR)
|
|
|
|
@for file in $(DISTFILES); do \
|
|
|
|
if test -d $$file; then \
|
|
|
|
mkdir $(DISTDIR)/$$file; \
|
|
|
|
else \
|
|
|
|
cp -p $$file $(DISTDIR)/$$file; \
|
|
|
|
fi; \
|
|
|
|
done
|
|
|
|
@tar -c $(DISTDIR) | gzip -9 > $(RELEASE_NAME).tar.gz
|
|
|
|
@rm -rf $(DISTDIR)
|
|
|
|
@echo "Built $(RELEASE_NAME).tar.gz"
|
2003-10-17 11:18:40 +07:00
|
|
|
|
|
|
|
|
2003-12-17 14:41:59 +07:00
|
|
|
ifeq ($(USE_DBUS), true)
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
install-dbus-policy:
|
|
|
|
$(INSTALL) -d $(DESTDIR)$(dbusdir)
|
2004-01-01 11:38:14 +07:00
|
|
|
$(INSTALL_DATA) etc/dbus-1/system.d/udev_sysbus_policy.conf $(DESTDIR)$(dbusdir)
|
|
|
|
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
uninstall-dbus-policy:
|
|
|
|
- rm $(DESTDIR)$(dbusdir)/udev_sysbus_policy.conf
|
|
|
|
else
|
|
|
|
install-dbus-policy:
|
|
|
|
-
|
|
|
|
uninstall-dbus-policy:
|
|
|
|
-
|
|
|
|
endif
|
|
|
|
|
2003-12-20 09:29:05 +07:00
|
|
|
install-config: $(GEN_CONFIGS)
|
2003-10-30 13:26:35 +07:00
|
|
|
$(INSTALL) -d $(DESTDIR)$(configdir)
|
2003-12-20 09:29:05 +07:00
|
|
|
@if [ ! -r $(DESTDIR)$(configdir)udev.conf ]; then \
|
2004-01-01 11:35:02 +07:00
|
|
|
echo $(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.conf $(DESTDIR)$(configdir); \
|
|
|
|
$(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.conf $(DESTDIR)$(configdir); \
|
2003-12-20 09:29:05 +07:00
|
|
|
fi
|
|
|
|
@if [ ! -r $(DESTDIR)$(configdir)udev.rules ]; then \
|
2004-01-01 11:35:02 +07:00
|
|
|
echo $(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.rules $(DESTDIR)$(configdir); \
|
|
|
|
$(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.rules $(DESTDIR)$(configdir); \
|
2003-12-20 09:29:05 +07:00
|
|
|
fi
|
|
|
|
@if [ ! -r $(DESTDIR)$(configdir)udev.permissions ]; then \
|
2004-01-01 11:35:02 +07:00
|
|
|
echo $(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.permissions $(DESTDIR)$(configdir); \
|
|
|
|
$(INSTALL_DATA) $(LOCAL_CFG_DIR)/udev.permissions $(DESTDIR)$(configdir); \
|
2003-12-20 09:29:05 +07:00
|
|
|
fi
|
|
|
|
|
|
|
|
install: install-config install-dbus-policy all
|
|
|
|
$(INSTALL) -d $(DESTDIR)$(udevdir)
|
2003-10-30 13:26:35 +07:00
|
|
|
$(INSTALL) -d $(DESTDIR)$(hotplugdir)
|
|
|
|
$(INSTALL_PROGRAM) -D $(ROOT) $(DESTDIR)$(sbindir)/$(ROOT)
|
2004-01-10 16:19:57 +07:00
|
|
|
@if [ "x$(USE_LSB)" = "xtrue" ]; then \
|
2004-01-13 12:17:22 +07:00
|
|
|
$(INSTALL_PROGRAM) -D etc/init.d/udev.init.LSB $(DESTDIR)$(initdir)/udev; \
|
|
|
|
ln -s $(DESTDIR)$(initdir)/udev $(sbin_dir)/rcudev; \
|
|
|
|
else \
|
|
|
|
$(INSTALL_PROGRAM) -D etc/init.d/udev $(DESTDIR)$(initdir)/udev; \
|
2004-01-10 16:19:57 +07:00
|
|
|
fi
|
2003-10-30 13:26:35 +07:00
|
|
|
$(INSTALL_DATA) -D udev.8 $(DESTDIR)$(mandir)/man8/udev.8
|
2003-11-23 20:58:21 +07:00
|
|
|
- rm -f $(DESTDIR)$(hotplugdir)/udev.hotplug
|
2003-12-20 09:29:05 +07:00
|
|
|
- ln -f -s $(sbindir)/$(ROOT) $(DESTDIR)$(hotplugdir)/udev.hotplug
|
2003-12-18 09:32:53 +07:00
|
|
|
@extras="$(EXTRAS)" ; for target in $$extras ; do \
|
2003-12-08 00:04:49 +07:00
|
|
|
echo $$target ; \
|
|
|
|
$(MAKE) prefix=$(prefix) LD="$(LD)" SYSFS="$(SYSFS)" \
|
|
|
|
-C $$target $@ ; \
|
|
|
|
done ; \
|
2003-10-17 14:19:04 +07:00
|
|
|
|
[PATCH] D-BUS patch for udev-008
Attached is a patch against udev-008 to send out a D-BUS message when a
device node is added or removed.
Using D-BUS lingo, udev acquires the org.kernel.udev service and sends
out a NodeCreated or NodeDeleted signal on the
org.kernel.udev.NodeMonitor interface. Each signal carries two
parameters: the node in question and the corresponding sysfs path.
[Note: the D-BUS concepts of service, interface, object can be a bit
confusing at first glance]
An example program listening for these messages looks like this
#!/usr/bin/python
import dbus
import gtk
def udev_signal_received(dbus_iface, member, service, object_path, message):
[filename, sysfs_path] = message.get_args_list()
if member=='NodeCreated':
print 'Node %s created for %s'%(filename, sysfs_path)
elif member=='NodeDeleted':
print 'Node %s deleted for %s'%(filename, sysfs_path)
def main():
bus = dbus.Bus(dbus.Bus.TYPE_SYSTEM)
bus.add_signal_receiver(udev_signal_received,
'org.kernel.udev.NodeMonitor', # interface
'org.kernel.udev', # service
'/org/kernel/udev/NodeMonitor') # object
gtk.mainloop()
if __name__ == '__main__':
main()
and this is the output when hot-plugging some usb-storage.
[david@laptop udev-008]$ ~/node_monitor.py
Node /udev/sda created for /block/sda
Node /udev/sda1 created for /block/sda/sda1
Node /udev/sda1 deleted for /block/sda/sda1
Node /udev/sda deleted for /block/sda
The patch requires D-BUS 0.20 or later while the python example program
requires D-BUS from CVS as I only recently applied a patch against the
python bindings.
2003-12-09 00:19:19 +07:00
|
|
|
uninstall: uninstall-dbus-policy
|
2003-10-17 14:19:04 +07:00
|
|
|
- rm $(hotplugdir)/udev.hotplug
|
2003-10-22 12:08:03 +07:00
|
|
|
- rm $(configdir)/udev.permissions
|
2003-12-03 16:08:46 +07:00
|
|
|
- rm $(configdir)/udev.rules
|
|
|
|
- rm $(configdir)/udev.conf
|
2003-12-17 14:30:15 +07:00
|
|
|
- rm $(initdir)/udev
|
2003-10-17 14:19:04 +07:00
|
|
|
- rm $(mandir)/man8/udev.8
|
|
|
|
- rm $(sbindir)/$(ROOT)
|
|
|
|
- rmdir $(hotplugdir)
|
|
|
|
- rmdir $(configdir)
|
|
|
|
- rmdir $(udevdir)
|
2003-12-18 09:32:53 +07:00
|
|
|
@extras="$(EXTRAS)" ; for target in $$extras ; do \
|
2003-12-08 00:04:49 +07:00
|
|
|
echo $$target ; \
|
|
|
|
$(MAKE) prefix=$(prefix) LD="$(LD)" SYSFS="$(SYSFS)" \
|
|
|
|
-C $$target $@ ; \
|
|
|
|
done ; \
|