Home » Mailing list archives » dragonflybsd-kernel » 2009 » July

dragonflybsd-kernel mailing list

FromSubjectsort iconDate
Hasso Tepper
Wishlist for unfrozen base
Compilers and stuff =================== * gcc 3.4 removal. There are two options - remove it entirely or just disable it by default (it still might be potentially useful, for example gcc34 in the pkgsrc will never support stack protection). Opinions? * gcc 4.x update. gcc 4.1.2 we use at the moment is too buggy - to the point where some projects ignore bugreports at all if gcc-4.1.x is in use (ffmpeg for example). We should decide what path to choose at all with it though. There i...
[ message continues ]
Jul 3, 5:42 am 2009
Matthew Dillon
Re: PCI code from FreeBSD
We can expand the number of vectors. The most annoying part will be changing gd_fpending and gd_ipending bitmaps into arrays. The assembly will have to be hardwired for two 32 bit bitmaps. -Matt
Jul 3, 1:19 am 2009
Matthew Dillon
Re: PCI code from FreeBSD
That would be cool. -Matt Matthew Dillon <dillon@backplane.com>
Jul 3, 12:44 am 2009
Sepherosa Ziehau
Re: PCI code from FreeBSD
On Fri, Jul 3, 2009 at 2:01 AM, Matthew I think before bringing the ACPI code, we have to change our APIC interrupt handling code: FreeBSD uses ACPI GSI (ACPI3.0a, page120) concept directly (I think they apply it to the MP table too). So more than 24 idt vectors may be used, if, for example, there are two 24pin I/O APICs. As far as I understand our apic_abi.c, we only support 24 idt vectors; and the gd_[if]pending limit us to 32 vectors. Before we could sort that out or at least introduce ano...
[ message continues ]
Jul 2, 9:50 pm 2009
Sepherosa Ziehau
Re: PCI code from FreeBSD
BTW, I prefer not to introduce another mapping layer, so we could prepare the MSI/MSI-X work :) Best Regards, sephe -- Live Free or Die
Jul 2, 9:54 pm 2009
Sepherosa Ziehau
Re: PCI code from FreeBSD
I could help you to get it into base system. Best Regards, sephe -- Live Free or Die
Jul 2, 9:52 pm 2009
Hasso Tepper
Re: PCI code from FreeBSD
As our current old PCI stuff has been on my way more than once and still is in some areas, I'll try to help as well. -- Hasso Tepper
Jul 3, 1:09 am 2009
Hasso Tepper
Re: Master release schedule changes, major feature list - Se...
This will mean the end of September and the end of March then - together with Q3 and Q1 pkgsrc releases? This might be a little racy as well. It might happen that pkgsrc release is delayed a little (like 2009Q2 is at the moment) and it takes a while to build packages as well. We might play with release/branch dates as well though - for example we branch when we are ready and really announce a release when pkgsrc packages are ready. And this will also mean that our userspace ABI/API/etc is unf...
[ message continues ]
Jul 3, 4:27 am 2009
previous daytodaynext day
July 2, 2009July 3, 2009None