Re: Porting DeviceKit-power to FreeBSD

2010-01-02 Thread Joe Marcus Clarke
On Fri, 2010-01-01 at 18:57 +, Richard Hughes wrote:
> 2010/1/1 Joe Marcus Clarke :
> > I tried, but evidently, I do not have permission to push to the
> > DeviceKit repository.  I have hal access, but I guess I need DK-p access
> > as well.
> 
> Hmm, I thought it was the original hal commit members. If you push
> something to gitweb or your private page then I'll try to clone from
> your tree.

I just generated some format-patches.  I didn't want to send them via
email because they're pretty big (but I can if you prefer).  I have
posted them at http://www.marcuscom.com/downloads/devicekit-power/ .  

The patch 0003-add-backend-support-for-obtaining-kernel-info.patch
should not be committed as-is.  It is my proof-of-concept on using the
backend to provide kernel info.  The method prototypes in dkp-backend.h
are probably safe, but I added #ifdef's to dkp-daemon.c.  I imagine you
may want to make some changes, so I didn't bother adding code to the
linux and dummy backends.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team  ::  gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome


signature.asc
Description: This is a digitally signed message part
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel


Re: signalling suspend/resume events (deviceKit-power)

2010-01-02 Thread Richard Hughes
2010/1/2 Bartłomiej Zimoń :
> I'm writing small kernel helper module to expose such info to userspace.
> What could be more prefferad to notify about suspend/resume: sysfs,procfs or 
> device file?

sysfs, preferably using a uevent or one-value-per-file please.

Richard.
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel


Re: signalling suspend/resume events (deviceKit-power)

2010-01-02 Thread Bartłomiej Zimoń
Dnia 2 stycznia 2010 22:53 Richard Hughes  napisał(a):
> 2010/1/2 Bartłomiej Zimoń :
> > I'm writing small kernel helper module to expose such info to userspace.
> > What could be more prefferad to notify about suspend/resume: sysfs,procfs 
> > or device file?
> 
> sysfs, preferably using a uevent or one-value-per-file please.
> 

For now it is device file witch on event send event id.
please look on discusion on today lkml topic: "userspace notification from 
module"

Best regards
Bartłomiej Zimoń
PLD Linux, Kadu Team
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel


How to make devkit automount the new class or removeable devices

2010-01-02 Thread Maxim Levitsky
Hi folks,
Could you save me some of my free time, and give me an advice on how to
make devicekit and higher level libraries recognize xD picture cards,
support for which I recently have written.
When I feel confident that it works, I will release it under GPL of
course.

Currently this is what I receive from udev:


The xD device:
UDEV  [1262469549.601179] change   /devices/virtual/mtd/mtd0/smblka (block)
UDEV_LOG=3
ACTION=change
DEVPATH=/devices/virtual/mtd/mtd0/smblka
SUBSYSTEM=block
DEVNAME=/dev/smblka
DEVTYPE=disk
SEQNUM=1694
ID_FS_UUID=1970-BEB3
ID_FS_UUID_ENC=1970-BEB3
ID_FS_VERSION=FAT32
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
DKD_MEDIA_AVAILABLE=1
DKD_PARTITION_TABLE=1
DKD_PARTITION_TABLE_SCHEME=mbr
DKD_PRESENTATION_NOPOLICY=0
MAJOR=4095
MINOR=0
DEVLINKS=/dev/block/4095:0 /dev/disk/by-uuid/1970-BEB3

--

The SD card, which is automounted correctly:
UDEV  [1262469429.481464] add  
/devices/pci:00/:00:1e.0/:07:00.1/mmc_host/mmc0/mmc0:8001/block/mmcblk0
 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci:00/:00:1e.0/:07:00.1/mmc_host/mmc0/mmc0:8001/block/mmcblk0
SUBSYSTEM=block
DEVNAME=/dev/mmcblk0
DEVTYPE=disk
SEQNUM=1679
ID_NAME=SD01G
ID_SERIAL=0x009cc3b6
ID_PATH=pci-:07:00.1
ID_FS_UUID=1DBA-773C
ID_FS_UUID_ENC=1DBA-773C
ID_FS_VERSION=FAT32
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
DKD_MEDIA_AVAILABLE=1
DKD_PARTITION_TABLE=1
DKD_PARTITION_TABLE_SCHEME=mbr
DKD_PRESENTATION_NOPOLICY=0
MAJOR=179
MINOR=0
DEVLINKS=/dev/block/179:0 /dev/disk/by-id/mmc-SD01G_0x009cc3b6 
/dev/disk/by-path/pci-:07:00.1 /dev/disk/by-uuid/1DBA-773C


Devicekit sees the xD device as a plain disk and doesn't automount it.
(I think that nautilus does the automounting though)


Best regards,
Maxim Levitsky

___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel