/dev/syl

Libusb-1.0 in head

2009-06-11T06:55:00.000-07:00

Hi everybody,

thompsa@ has imported my work on libusb-1.0 emulation into head. Feel free to test and report me any bugs :)

FYI isochronous and interrupt transfers are not supported for the moment (in reality not yet tested).

If you want some code example of libusb-1.0 you can have a look at the testing programs that I used to validate this library here.

I will try to send a mail to freebsd-ports@ to update the package which used libusb-1.0.

Feel free to mail me or freebsd-usb@ if you have any question on libusb-1.0 emulation.

Cheers,

coding begins

2009-05-23T01:43:00.000-07:00

Hi,

The summer of code begins today.

I've already received goods from Google. The first one is an account on acm :) The second one is in Memphis for the moment and it is my prepaid card with 500$ with google stickers :)

Concerning the code for freebsd, I've already started to work on libusb-1.0 and I have nearly implemented it due to the graceful help of Hans Petter Selasky \o/.

If someone would test or have a look at the libusb-1.0 emulation into FreeBSD just go there. It is all the files prefixed by libusb10. I will try to finish the libusb-1.0 support soon to go into the kernel :)

Cheers,

FreeBSD Google Summer of Code

2009-04-22T00:36:00.001-07:00

Hi,

Just a little post to tell you that I will participate in the fifth google Summer of Code for the FreeBSD project. My work will focus on USB.

If you want some news on my subject you can find them on the FreeBSD wiki :

This project will probably freeze the current PMBSD development and all my other little projects during the summer time.

I will try to put news of the google Summer of Code on this blog when I have the time during the Summer.

Cheers,

FreeBSD current Xorg and hp2133

2009-04-06T04:50:00.000-07:00

Hi,

I've had some difficulties with xorg installation on the hp2133. This installation is not trivial so if you don't manage to do it, you can follow this howto :)

You need to have an updated ports source tree. If you don't have any /usr/ports directory you need to do that :

cd /usr/

cvs -danoncvs@anoncvs.fr.freebsd.org:/home/ncvs checkout -P ports.

you already have an /usr/ports dir you only need to update :

cd /usr/ports cvs update -Pd

Now let's compile Xorg :

cd /usr/ports/x11/xorg
make && make install.

You can have some problem to compile it with randr, to fix it you can do this:

cd /usr/ports/x11/randrproto/ make && make deinstall && make install
cd /usr/ports/x11/libXrandr/ make && make deinstall && make install
cd /usr/ports/x11/xrandr/ make && make deinstall && make install
cd /usr/ports/x11/xorg/ make && make install

Now you have xorg installed, but if you try to launch it with a startx your laptop hangs. You need to update the openchrome driver from the openchrome directory:

cd ~/
make code
cd code
svn co http://svn.openchrome.org/svn/trunk/
cd trunk/
./autogen.sh --prefix=/usr/X11R6
make && make install

Now you have a working X but the mouse and the keyboard don't respond... You need to enable in your rc.conf the dbus and hal:

echo hald_enable=YES >> /etc/rc.conf
echo dbus_enable=YES >> /etc/rc.conf

Now averything works fine.

HTH,

Install FreeBSD current on hp2133

2009-04-06T04:32:00.000-07:00

Hi,

Last week, I tried to install FreeBSD current on my hp2133. I had some problems to install it so here is how I did it.

First this laptop has no cdrom, so I installed FreeBSD on it with an usbkey. You need to take another laptop with a FreeBSD and checkout the sources :

cd /usr

cvs -danoncvs@anoncvs.fr.freebsd.org:/home/ncvs checkout -P src

After that you have to build the system for the usb key:

make buildworld
make buildkernel KERNCONF="GENERIC"

When the userland and the kernel are compiled you need to prepare the usb disk :

fsdisk -I /dev/da0
fdisk -B /dev/da0
bsdlabel -w /dev/da0s1a auto
bsdlabel -B /dev/da0s1a
newfs /dev/da0s1a
mount /dev/da0s1a /mnt

Now the disk is mounted & you need to install the binaries on it:

make installworld DESTDIR=/mnt
make installkernel DESTDIR=/mnt KERNCONF="GENERIC"
make distrib-dirs DESTDIR=/mnt
make distribution DESTDIR=/mnt
echo /dev/da0s1a / ufs rw 1 1 > /mnt/etc/fstab
echo hostname="myname" > /mnt/rc.conf
cp -fr /usr/src /mnt/usr/.

Now you can boot with the usb key on the hp2133. Warning: during the bootloader you must boot in failsafe mode, because there are an apic problem on current with the laptop...

When you have booted you can log with the root account without password. Now you need to recompile the userland and the kernel but instead installing it on da you can do it on ad (your disk drive) :

make buildworld
make buildkernel KERNCONF="GENERIC"
fsdisk -I /dev/ad0
fdisk -B /dev/ad0
bsdlabel -w /dev/ad0s1a auto
bsdlabel -B /dev/ad0s1a
newfs /dev/ad0s1a
mount /dev/ad0s1a /mnt
make installworld DESTDIR=/mnt
make installkernel DESTDIR=/mnt KERNCONF="GENERIC"
make distrib-dirs DESTDIR=/mnt
make distribution DESTDIR=/mnt
cp /etc/rc.conf /etc/fstab /mnt/etc

Now you can remove your usb key and boot on your hp2133 drive :)

HTH

AT91SAM9261-EK on FreeBSD.

2009-03-24T02:11:00.001-07:00

Hi everybody.

Its been a couple of days thatI am trying to port the at91sam9261 SoC on FreebSD and the AT91SAM9261 Evalution Kit.

After two or three day of debugging and developing I finished to boot the card and to have a sexy dmesg that hang on the NFS init. (that's normal because I haven't got implemented the ethernet driver card yet).

If you want some other information about the at91sam9261ek board you can find the datasheets of its SoC here, its schematics here and a picture of this board here.

You can find the dmesg here, the patch here and follow the submit on mailling list here.

If you have any question about this patch and want to mail me about it, you're welcome :)

See you in a next post :)

PCI

2009-02-22T08:20:00.001-08:00

Hello.

This week we are going to talk about PCI. PCI has from 0 up to 254 buses. On each bus you can have devices (maximum 32). The device can have many functions (up to 8). These functions could be useful if you are using a device which has multiple functionality. For example a Video acquisition card could have a function 0 for video acquisition and a function 1 for sound acquisition, etc etc... Some systems, like Linux have some abstraction over pci to handle big super computer configuration that has more than 256 pci. For that they use domains of buses which can have 256 buses each.

Each PCI slot has four interrupts possible (One per interrupt pin (A to D)).

PCI configuration space.

For a set of bus:device:functions you have a trame of 256 bits of data. This trame is called configuration space. the config space looks like :

Warning PCI registers are always little endian.

All the values present in this 256 bits chunk can be read or written (I think that some value are just read-only like the vendor ID or product ID).

Base address is an interesting value because it helps us to know the type of registers (IOports or memory). It helps us to know where the registers start in memory or iospace and where it ends.

For irq the line is present in the 60th bit of the chunk. This bit is set to 0 if the device doesn't support IRQ.

PMBSD

2009-02-06T04:30:00.000-08:00

Hello,

You can find here, my newblog specialised in the project Pigeon Mouette BSD.

If you have free time and have interest in kernel or driver development contact me; pmbsd needs more hackers to be operational.

For the moment pmbsd is in version 0.1 but will have an userland for the version 0.3.

PCC C extensions

2008-08-24T02:15:00.000-07:00

Hi,

It's been a while that I wanted to know how PCC (Portable C Compiler) works . So I decided to use it for ksyl (my own educational kernel). I've been thinking that if pcc compiles the whole userland of OpenBSD and whole kernelland with some patches, then it must work with my own kernel :)

The first step for me is to fetch the source of pcc on my desktop and I am lucky because the source tree of my OS has it. So I just need to checkout pcc and compile it:

cvs -danoncvs.de.openbsd.org:/cvs co -P src/usr.bin/pcc
cd src/usr.bin/pcc
make depend && make && make install

Now I ve got a pcc binary and a cpp binary in /usr/local/bin/. So I need to fix the CC var in the ksyl Makefile :

CC = /usr/local/bin/pcc.

Everything seems to be ok, now I will try to compile ksyl :

ksyl@rincewind {4}> make

And then appears the first error :

include/./sys/gdt.h, line 15: syntax error
include/./sys/gdt.h, line 15: invalid function definition
include/./sys/gdt.h, line 15: syntax error
include/./sys/gdt.h, line 21: syntax error
include/./sys/gdt.h, line 21: invalid function definition
include/./sys/gdt.h, line 21: redeclaration of packed
include/./sys/gdt.h, line 21: syntax error
include/./386/idt.h, line 26: syntax error
include/./386/idt.h, line 26: invalid function definition
include/./386/idt.h, line 26: redeclaration of packed
include/./386/idt.h, line 26: syntax error
include/./386/idt.h, line 32: syntax error
include/./386/idt.h, line 32: invalid function definition
include/./386/idt.h, line 32: redeclaration of packed
include/./386/idt.h, line 32: syntax error

These errors came from the different gcc extentions needed to do packing like __attribute__((packed)). The packing of the structure included into gdt.h and idt.h allowed ksyl to work properly. Thus I googled "pcc packing" to find a solution without success to finally.... have a look in pcc sources. I found the solution in the pcc lexer. I must used a pragma :

#pagma pack(1)
struct idt
{
...
};
#pragma pack

After the patch I try to compile it :

ksyl@rincewind {4}> make
ksyl -> compilation OK

All works \o/

syscalls...

2008-05-20T04:47:00.000-07:00

Hello everybody.

TUHS (The Unix heritage society) guys are very impressive.

During the last two days Warren Toomey has been talking about syscall implementation in Unix V1. There are the following 33 syscalls :

V1_RELE 0 /* release the CPU, i.e. pre-empt this process */
V1_EXIT 1 exit()
V1_FORK 2 fork()
V1_READ 3 read()
V1_WRITE 4 write()
V1_OPEN 5 open()
V1_CLOSE 6 close()
V1_WAIT 7 wait()
V1_CREAT 8 open(path, O_CREAT O_TRUNC O_WRONLY, mode);
V1_LINK 9 link()
V1_UNLINK 10 unlink()
V1_EXEC 11 exec()
V1_CHDIR 12 chdir()
V1_TIME 13 gettimeofday()
V1_MKDIR 14 mkdir()
V1_CHMOD 15 chmod()
V1_CHOWN 16 chown()
V1_BREAK 17 brk()
V1_STAT 18 stat()
V1_SEEK 19 lseek()
V1_TELL 20 lseek(fd, 0, SEEK_CUR);
V1_MOUNT 21 mount()
V1_UMOUNT 22 umount()
V1_SETUID 23 setuid()
V1_GETUID 24 getuid()
V1_STIME 25 settimeofday()
V1_QUIT 26 signal(SIGQUIT,...)
V1_INTR 27 signal(SIGINT,...)
V1_FSTAT 28 fstat()
V1_CEMT 29 signal(SIGEMT,...)
V1_SMDATE 30 utimes()
V1_STTY 31 fcntl(), tcsetattr()
V1_GTTY 32 fcntl(), tcgetattr()
V1_ILGINS 33 signal(SIGILL,...)

With it Unix v1 offers :

- a multitasking system with up to 16 processes
- multiple users- a hierachical filesystem, with empty directories used as mountpoints
- read/write file protection for user/other (no group), plus the execute and set-userid bits
- i-nodes, and filenames separated from i-nodes, allowing hard links
- device files

It's amazing that modern Unices operating systems keep being unchanged since 1971 (37 years) :)

USB Conference

2008-05-01T11:57:00.001-07:00

Hi guys,

I did a conference on usb architecture and development at Epitech on Wenesday 30 april.

The conferance was cool, and some people ask me to post my slides on my blog. So I do it here :)

The slide is not very verbose, but perhaps some people are going to used it one day.

ps : some part of the slide are thiefed on beyonlogic and it s very interesting and helpfull usb in a nutshell.

nostalgie

2008-04-23T00:44:00.000-07:00

Hi everybody,

I found this pdf which seem to be very funny. Someone was talking about it this night on THUS. So for those who don't know this paper have a good time reading it:)
linkofthedead
manofthedead

Ksyl is alive

2008-03-29T06:18:00.000-07:00

Hi everybody,

Let me introduce you ksyl. Ksyl is a simply, educational and monolithic kernel.

I have started it one month ago and I am going to continue to work on it to try to understand the way it basically works.

At this moment the version 0.0.0.1 of ksyl has just been released and can just boot. It contains a bootloader in asm, and a little kernel in C.

The kernel just contains a very simple gdt and idt management, the begining of a vga driver and a big while(42).

I will try in my future post to describe all the parts of ksyl and how it works :)

See you soon!

rathaxes lkm

2008-03-04T07:12:00.001-08:00

Hi everyone.

I've got some news about the rathaxes project. The first one is that we have achieved the first step named : Loadable Kernel Module.

We have described how to develop lkm on the four main platforms : OpenBSD, MacOSX 10.5, Linux and Windows Xp into a paper in destination at language team. You can download this paper here.

The language team has worked on our paper and has implemented the lkm generation. We are now able to generate kernel driver with this simple syntax :

DEVICE
{
 NAME = my_device;
};

INSTANCIATE
{
NAME = my_device;
ARCH = macOS;
};

I will repost some news about rathaxes as soon as intersting change arrives. To follow the rathaxes project advancement click here.

xnu uio api

2008-01-28T05:05:00.000-08:00

Hello guys,

Since few days I implement a simple rs232 driver on Darwin. But during this implementation I have got some understand problem about a data structure.

Today I will introduce you a part of the kpi : the struct uio and a lot of conveniance functions about uio. And this api is the sources of my past problems. But after my explication I will seem dumb because uio is very simple to understand and to implement.

Uio what s that ? Its simply a api to work with data buffer. Which is the relationship between the rs232 and the struct uio? The functions pointer you ll need to implement to register your driver use uio (like the read or write). Why is this destabilizing? because the struct uio is defined like that in the uio header :

struct uio;

So we don't know the members of that structure. Why apple does that? Because they want to be able to change the code managing this data without the change of all the code using this api.

an uio is a container of iovec. It can have one iovec or a collections of iovec. The iovec contains data. the iovec structure looks like :

struct iovec

{

void *iov_base;

size_t iov_len;

}

This API offers some functions to work on uio containing just one iovec :

void uio_setresid( uio_t a_uio, user_ssize_t a_value );
int uio_rw( uio_t a_uio );
void uio_setrw( uio_t a_uio, int a_value );
int uio_isuserspace( uio_t a_uio );

for collections of data uio struct can work with this fuctions :

int uio_iovcnt( uio_t a_uio );
uio_t uio_create( int a_iovcount, off_t a_offset, int a_spacetype, int a_iodirection );
void uio_reset( uio_t a_uio, off_t a_offset, int a_spacetype, int a_iodirection );
uio_t uio_duplicate( uio_t a_uio );
void uio_free( uio_t a_uio );
void uio_update( uio_t a_uio, user_size_t a_count );
user_ssize_t uio_resid( uio_t a_uio );

int uio_iovcnt( uio_t a_uio );
off_t uio_offset( uio_t a_uio );
void uio_setoffset( uio_t a_uio, off_t a_offset );
user_addr_t uio_curriovbase( uio_t a_uio );
user_size_t uio_curriovlen( uio_t a_uio );
int uio_addiov( uio_t a_uio, user_addr_t a_baseaddr, user_size_t a_length );
int uio_getiov(uio_t a_uio, int a_index, user_addr_t *a_baseaddr_p,

user_size_t * a_length_p );
off_t uio_offset( uio_t a_uio );
void uio_setoffset( uio_t a_uio, off_t a_offset );

My rs232 driver read and write exemple :

/*
** Serial read, read one byte from the device
*/

int serial_read(dev_t dev, struct uio *uio, int ioflag)
{
struct device *current;
int len;
int rlen;
char buff[1];
int size= 1;
int i;

*buff = 0;
if (uio_rw(uio) != UIO_READ)
return (EINVAL);
if (minor(dev) >= MAX_PORTS)
return (ENXIO);
current = &serial[minor(dev)];
if (!(current->attached))
return (EBUSY);
len = uio_resid(uio);
rlen = MIN(size, len);
for (i = 0; i <>

{

while(((inb(current->port + LSR)) & 0x01) == 0);
buff[i] = inb(current->port + RECEIVER);
}
uiomove(buff, rlen, uio);
printf(DEVICE_NAME " READ\n");
return KERN_SUCCESS;
}

/*
** Serial write, write n bytes to the device
*/

int serial_write(dev_t dev, struct uio *uio, int ioflag)
{
struct device *current;
int len;
char *buff;
int i;

if (uio_rw(uio) != UIO_WRITE)
return (EINVAL);
if (minor(dev) >= MAX_PORTS)
return (ENXIO);
current = &serial[minor(dev)];
if (!(current->attached))
return (EBUSY);
len = uio_resid(uio);
MALLOC(buff, char *, len * sizeof(*buff), M_WAITOK|M_ZERO, M_TEMP);
if ((uiomove(buff, len, uio)) != 0)
{
printf(DEVICE_NAME "KPI error");
return KERN_FAILURE;
}
for (i = 0 ; i < style="text-align: justify;"> {

while((inb(current->port + LSR) & 0x20) == 0);
outb(current->port + TRANSMITTER, buff[i]);
}
FREE(buff, M_WAITOK|M_ZERO);
printf(DEVICE_NAME " WRITE\n");
return KERN_SUCCESS;
}

Unix V7

2008-01-23T08:30:00.000-08:00

Hello,

I found here a mail of mr nordier who says "hey I made the x86 V7 port do you want it".

Grrr I need more time to read interesting sources like these. If you want to see the Project Page.

Paid to do kernel land stuff

2008-01-04T00:04:00.000-08:00

Since the 5th of November I start my new job at Adeneo and it's the first time in my life where I was paid to do kernel land stuff :)

The first step job this is a one month formation on Windows CE 6.0 and diverse embedded cpus. Before my first day I'd just have some bad feeling about CE development because it wasn't unix kernel development, but when the formation start I realize that I was totally wrong. This job is really interesting for a lot of reasons:

- Co-Workers seems to be good workers and C lovers. They are a great source of information.
- With a very quick and interesting formation this permits me to learn a lot of things in just two weeks...
- CE6.0 permits to browse all of the kernel land and user land source, and it s funny to read the ie or cmd sources :)
- The code I have to realize is not ugly like some C# or another ugly, sad or insane thing. It's just C, C++ or asm. It was some code very near the hardware.
- I start my work on a atmel chip that was an architecture very different from the ugly x86.
- CE permit me to see another kernel code implementation. With that I can find better code abstraction in driver development.
- I can continue my personal development in unix and free software and continue to work on some project or create new one...

Links:
Adeneo Website
Windows embedded developper center
wiki on winCE

advancement on sos

2008-01-03T23:54:00.001-08:00

A little new post to keep you aware of the advancement of the sos framebuffer driver.

Right now, Buckman and I have finished the vm86 driver, allowing us to call 16bits bios interrupts from kernel land. Thanks to this vm we will be able to call the vesa functions, reachable only through 16 bit modes.

Bios interrupts are called just like in this piece of code, that allows us to get some infromation from the VBE:

vbe_info_block_t *get_vbe_info()
{
vbe_info_block_t *vbe;
sos_vm86_t regs;
memset(&regs, 0, sizeof(sos_vm86_t));
regs.service = 0x10;
regs.ax = VBE_INFO;
regs.es = SOS_VM86_SEGMENT;
regs.di = vbe = sos_vm86_malloc(sizeof(*vbe));
strzcpy(vbe->vbe_signature, "VBE2", 4);
sos_vm86_bioscall(&regs);
return (vbe);
}

In a first time we will memset the structure to be sure it is initialised to 0. Then we will fill the vm86 structure with the data corresponding to interruption 0x10 and the data for this interruption in the virtual registers ax es and di. And then we call the function sos_vm86_bioscall that wraps around the interrupt. The data structure sos_vm86_t is defined as :

typedef struct
{
sos_ui8_t service; /* Numero de l interruption a appeler*/
sos_ui16_t ax;
sos_ui16_t bx;
sos_ui16_t cx;
sos_ui16_t dx;
sos_ui16_t si;
sos_ui16_t di;
sos_ui16_t es;
sos_ui16_t ds;
} sos_vm86_t;

In a second time we coded the vesa driver wich is a simple set of convenience functions. Here is the exhaustive list of vesa functions prototypes :

void init_vesa(sos_ui16_t mode);
vbe_info_block_t *get_vbe_info();
void map_lfb(mode_info_block_t *mib);
void set_display(sos_ui16_t mode);
mode_info_block_t *get_mib_info(sos_ui16_t mode, vbe_info_block_t *vbe);
sos_bool_t is_mode_usable( sos_ui16_t mode, vbe_info_block_t *vbe);
void vesa_clear_screen(mode_info_block_t *mib, sos_ui32_t color);
void vesa_draw_rect(sos_ui32_t startx, sos_ui32_t starty, sos_ui32_t
height, sos_ui32_t width, mode_info_block_t *mib,
sos_ui32_t color);
void vesafont_draw_text(const char* s, sos_ui32_t x, sos_ui32_t y,
sos_ui32_t fg, sos_ui32_t bg,
mode_info_block_t *mib);
void vesa_draw_bitmap(sos_ui32_t x, sos_ui32_t y, sos_vaddr_t *img);
void vesa_plot_pixel(sos_ui32_t x, sos_ui32_t y, mode_info_block_t *mib,
sos_ui32_t color);

It represents our virtual machine with a set of register and the id of the interrupt to call.

For the moment, we still have to work on the tty driver and the chardev /dev/fb.

To be concluded...

Implement a framebuffer on SOS

2008-01-03T23:50:00.000-08:00

Matthieu bucchianeri (buckman) and I started this Monday 15th of October the portage of a framebuffer on SoS[1].

This ports contains 3 great parts:
- The vm86 driver
- The vbe driver
- The vesatty driver

The vm86 driver permits to do bioscall in protected mode. This driver was finish and works fine :).

The vbe driver is a set of conveniences functions to set the config of the fb to map the memory of the db , to get vbe structure etc... This driver is completed at 75%. We have a mystical bug because our driver works fine on qemu but doesn t work on a GeForce2 with vbe3 support....

The last driver permits to replace the current console print by a framebuffer print but it is not yet started.

We took contact with the sos' developers to know if they wan't our kernel patch and a new article for GNU/Linux magazine. I will keep you informed about the advancement of this project.

[1]SimpleOS

zobfs

2008-01-03T23:45:00.000-08:00

The goal of the evilkittens October coding party for Filth and me was to create our first filesystem : the zobfs.

What is zobfs? Simply a port from scratch of a fat32 fs on OpenBSD. The aim of zobfs is to learn and understand how we can develop a filesystem on our favorite operating system.

We based our dev on some documentation about the fat32 specs and some OBSD fs howto:

fat32
Doc Open

Our project have a free CVS hosting offered by veins on evilkittens and you can browse the source on this cvsweb :

cvsweb

I hope we'll have finished this project for December. And I promise you a simple and sexy paper under LateX which explains how we implement this fs :)

my new job

2008-01-03T23:42:00.000-08:00

Hello, I'm writing a new post to talk about my hypothetical new job at Adeneo.

Do you now what is a BSP. A BSP is a Board support package, that means a package of file needed to port an os on a new architecture.

Why do I talk about BSP? Because my future job possibly concerns it. I will certainly work for the R&D of Adeneo to make the State-of-the-art of the differents BSP. When I will have finish the research job I will made some papers about it and perhaps start to think about a BSP generator.

With the Driver generator and the Stack Ip generator, this third project ensures the idea that the two next years should be generation years :)

Rataxes

2008-01-03T08:49:00.000-08:00

In the epitech cursus we have to realize a project named PFE (end of curses project). That s why we created rathaxes.

Rathaxes <1> will be a multi platform driver generator. This idea hinges around the fact that developping drivers is a difficult task because it requires developpement skills and electronic ones. Moreover the driver's specific code of an operating system is huge (about 70% for Linux) and this code is more buggy than other applications (7 times more).

To start we are going to use laurent reveillere's works and his thesis ''Approche langage au développement de pilotes de périphériques robustes" <2>. In this thesis, reveillere introduces the DSL/Driver concept. A DSL stands for Domain Specific Language, it is like SQL for the domain of databases.

For this project we will be helped by the LSE (System Laboratory of Epita) during the next two years<3> and his chief Lionel Auroux.

Liens :

<1> Rathaxes

<2> Thesis

<3> LSE