Re: Various size of (Project) ideas for NetBSD and pkgsrc
net...@precedence.co.uk (Stephen Borrill) writes: On Fri, 4 Oct 2013, Patrick Welche wrote: I might add some projects encountered during this morning's work: - add HVM support to xen 4 (Maybe part of Support latest features of Xen) - add snapshot support to lvm I'd add multipathing (MPP and RDAC) too. Not within LVM, but lower level as a virtual SCSI bus like Linux does. What's bad with the native Linux multipathing? This operates on the same level as LVM.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On 10/02/2013 11:13 AM, Martin Husemann wrote: On Wed, Oct 02, 2013 at 11:01:47AM +0200, Sergio Lopez wrote: On 10/02/2013 09:59 AM, Martin Husemann wrote: On Wed, Oct 02, 2013 at 09:15:48AM +0200, Sergio Lopez wrote: without changes. I think we just need an OpenFirmware replacement, some device drivers, and the usual bunch of tweaks here and there. The just need an OpenFirmware replacement part scares me big time. Is there any practical use in this? Well, perhaps saying OpenFirmware replacement was a bit of an exaggeration. I mean in the whole project - is it more than an academic example? Are there boards like this used for anything in practical ways? AFAIK, is being used for both academic and industrial purposes, but I suppose the latter are mostly Gaisler customers (the European Space Agency was a prominent one). Personally, it appeals to me because its an European (well, mostly) synthesizable GPL'ed processor, but I don't expect to see any LEON based computers in the mass market in a near future ;-) Sergio.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On 09/29/2013 08:41 PM, Ryo ONODERA wrote: (b) Porting NetBSD to OpenRISC 1200 (target board is not specified) Precisely a few weeks ago I've started playing around the idea of doing a or1k port. I've managed to build a stub-filled or32 kernel, and now I've dealing with the early CPU/MMU initialization. I'm targeting the architectural simulator (or1ksim), and I think is quite feasible as a project, but as I can only dedicate a few hours per week, I can't guarantee results. (d) Porting NetBSD to FPGA board with SPARC CPU softcore (target CPU and board is not specified) As we already have SPARCv8 support, this should be fairly easy. In fact, I've tried running a MRCOFFEE under TSIM (LEON3 emulator) and most of the hard and ugly low-level stuff (CPU, MMU, PIC...) seems to work without changes. I think we just need an OpenFirmware replacement, some device drivers, and the usual bunch of tweaks here and there. The bad news is that TSIM is proprietary software with a license fee. Perhaps Aeroflex Gaisler would donate some licenses for such a porting project, but I'm not sure about this. Sergio.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On 10/02/2013 09:59 AM, Martin Husemann wrote: On Wed, Oct 02, 2013 at 09:15:48AM +0200, Sergio Lopez wrote: without changes. I think we just need an OpenFirmware replacement, some device drivers, and the usual bunch of tweaks here and there. The just need an OpenFirmware replacement part scares me big time. Is there any practical use in this? Well, perhaps saying OpenFirmware replacement was a bit of an exaggeration. Gaisler, in its mklinuximg package, provides a GPL'ed PROM which implements vectors according to the OpenBoot specification. This needs a deeper analysis, but I think there are three options: 1) Adopt Gailer's PROM 2) Write our own BSD licensed PROM 3) Ignore the OpenBoot spec and make the kernel do its own way through the hardware. Sergio.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On Wed, Oct 02, 2013 at 11:01:47AM +0200, Sergio Lopez wrote: On 10/02/2013 09:59 AM, Martin Husemann wrote: On Wed, Oct 02, 2013 at 09:15:48AM +0200, Sergio Lopez wrote: without changes. I think we just need an OpenFirmware replacement, some device drivers, and the usual bunch of tweaks here and there. The just need an OpenFirmware replacement part scares me big time. Is there any practical use in this? Well, perhaps saying OpenFirmware replacement was a bit of an exaggeration. I mean in the whole project - is it more than an academic example? Are there boards like this used for anything in practical ways? Btw, the most easy way to hack around OF for sparc is probably to provide a promlib variant that hardcodes all functions for the concrete hardware and supply a custom bootloader. Martin
Re: Various size of (Project) ideas for NetBSD and pkgsrc
Ryo ONODERA wrote: (8) Porting NetBSD to some FPGA CPU board OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is available for FPGA board. At least OpenRISC 1200 and MicroBlaze have Linux support. Supporting these architecture is interesting for NetBSD. (I have no idea about NetBSD/nios2 status.) It could be worth splitting this task into core CPU work and writing drivers for peripheral devices. OpenCores drivers could be used by OpenRISC, Mico32, NetBSD/evbarm on the TS7300 or even in a PCI FPGA card. The Xilinx drivers would be needed by any port to MicroBlaze and by a port to the Zynq (arm) FPGAs. Robert Swindells
Re: Various size of (Project) ideas for NetBSD and pkgsrc
Hi, From: Alistair Crooks a...@pkgsrc.org, Date: Mon, 30 Sep 2013 04:26:07 +0200 [+Cc: tech-pkg - agc] Thanks for the list of suggestions - very useful and thought-provoking! On Sun, Sep 29, 2013 at 10:09:53AM +0900, Ryo ONODERA wrote: (2) Create multiple packages from one pkgsrc package directory For example, pkgsrc/fonts/harfbuzz has icu option and theoretically non-icu part and icu part can be separate package, but splitting only icu part from harfbuzz is difficult in configure/build stage. In rpm (Red Hat package manager) case, build once and multiple packages is created is realized with custom do-install target. build once means reduce of build time. We discussed this some time ago - this is what OpenBSD used to call FLAVORS, if I'm not mistaken, and then we (pkgsrc) defined flavors to mean something else entirely. Now just because we discussed something a while ago doesn't mean to say that we can't revisit the discussion, but I'm not sure what the benefits of the proposed change are. The way I see it, if I as a normal user wants to build a package, I know what options I want, and have them set already ahead of time. Having two separate binary packages with different options on the same machine is an unusual use case, and not something I'd recommend from a tearing hair out PoV. And if it's meant for the bulk builders, then this is usually done on larger machines, where any gain would be minimal. On the build machines, for building multiple versions of the same package, typically we'd have to build once with one configuration, then delete and re-configure with the new configuration, and continue until binary packages with individual options are built. To avoid leakage of one option into the next, I don't see there's any other way (although I might be missing something?) So in the whole scheme of things, what benefit would we get from this? Next thing, which is orthogonal, is that the different binary packages would have to be marked in some way with the options with which they were built, if we're going to live in a multi-option multiple package world. (This world does not scale well, but that, too, is orthogonal). So that I can install the harfbuzz+icu package on one machine, or one LOCALBASE, and the harfbuzz-icu package on another. I speak from experience - I used to have a copy of a statically-linked tcsh which I carried around with me, and one of the admins had a dynamically linked one; this is before, and the direct reason for creating, standalone-tcsh. (Actually, size of the package and contents was the principal way of deciding what was installed, but it was a pain to have to do that, and it, too, did not scale). Now I'm probably missing a whole lot of what's intended here, but I can't see it being a useful addition, or much of a win, for pkgsrc in general. Can you help me see what's whooshed over my head, please? I belive that multiple packages from one package directory is useful. (6) Porting Chromium web browser to NetBSD I have not tested build of Chromium (open source edition of Google Chrome), and I have a few experience about Google Chrome. Chromium may be useful web browser for NetBSD. Last I heard, Christos had this building - he certainly committed a number of fixes to src to make this build, but it's such a large thing that I don't personally have the resources to build it. IIRC, 16 GB RAM was the killer for me. Hmm... According to LinuxBuildInstructionsPrerequisites document at project's site, 8 GB RAM is lower limit. http://code.google.com/p/chromium/wiki/LinuxBuildInstructionsPrerequisites I have no 4 GB over RAM machine... (7) Apache OpenOffice for NetBSD I have completely no idea about Apache OpenOffice. It may be one of the most important application. Sounds like we're starting to get a number of forks of this, which isn't surprising. I think most people have migrated to libreoffice, is that a viable alternative in your view? I am working on LibreOffice 4.1.1.2 now. See pkgsrc-wip/libreoffice4. A administrator of famous anonymous ftp site in Japan says Apache OpenOffice is downloaded more than several times LibreOffice. I have heard LibreOffice is more easy to build than Apache OpenOffice, and I have started to package LibreOffice. But name of OpenOffice is more famous than LibreOffice at least in Japan. So some people will want to use it. (9) Add Microsoft's Hyper-V support to NetBSD There is two types of Hyper-V, Windows Server 2012's Hyper-V and Windows Server 2012R2's Hyper-V. I have heard Windows Server 2012's Hyper-V is supported on FreeBSD. But I cannot find the code for it. Similar to NetBSD/azure? http://wiki.netbsd.org/projects/project/netbsd_on_microsoft_azure/ Yes, this would be neat. :-) (14) commit mail of www.pkgsrc.org wiki I have heard some difficulties, but I do not know it in detail. If you can find out what this is, I'd be interested (and suspect
Re: Various size of (Project) ideas for NetBSD and pkgsrc
Le 29/09/13 20:41, Ryo ONODERA a écrit : Hi, From: Yann Sionneau yann.sionn...@gmail.com, Date: Sun, 29 Sep 2013 19:37:14 +0200 Hi Ryo, Le 29/09/13 03:09, Ryo ONODERA a écrit : Hi, (8) Porting NetBSD to some FPGA CPU board OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is available for FPGA board. At least OpenRISC 1200 and MicroBlaze have Linux support. Supporting these architecture is interesting for NetBSD. (I have no idea about NetBSD/nios2 status.) I am in the process of adding support for LatticeMico32 (LM32) architecture to NetBSD 6 kernel. Last year a MMU (memory management unit) has been added to the LM32 softcore which makes it able to run Linux or NetBSD. LM32 already had a uCLinux (noMMU) working port. This year I started the project to port NetBSD 6 kernel on MMU-enabled LM32 CPU in general and on the Milkymist open source System-on-Chip in particular. Today I had my first result on this project: http://pastebin.com/MJgB6Y05 - NetBSD 6 kernel immediately panics and dies. Even though this might - seem like a poor result, there have been a lot of work behind it. This is a first step which looks very promising :) (at least console driver works ;)) Great work! I am not kernel developer, but I want to know the following questions. How about status of NetBSD current? According to NetBSD development process, porting to current is essential, if I understand correctly. Sorry I was using wrong term by saying NetBSD 6 maybe. My work is based on -current But it's been several months since I last merged back into current so I'm a bit outdated I guess... But I don't think the kernel as changed so much that it would take more than a few hours to sort out how to merge correctly my branch with NetBSD-current :) And how about bus support? According to MiklyMist wiki, MilkyMist uses wishbone like bus, and I understand correctly, wishbone or similar bus support are not implemented in current NetBSD. Wishbone is the on-chip bus used in the System-on-Chip. It's totally transparent to the software. Basically all of the cores in the system-on-chip have a set of registers which are memory mapped. So there is no need for a bus support, or maybe something trivial like mapping those registers to virtual memory once and then use the mapping in the respective drivers of the different cores connected to the wishbone bus. Here is a block diagram of the Milkymist SoC: https://en.wikipedia.org/wiki/File:Milkymist_architecture.svg The Milkymist System-on-Chip runs on various FPGAs (Spartan 3, Spartan 6, Virtex 4 etc) from various FPGA vendors (Xilinx, Lattice, Altera) It has been ported on numerous boards (Milkymist One, ML401, De0-nano, Nexys3 etc...) It uses LatticeMico32 (open source softcore) as it's CPU softcore. If you want more information about Milkymist and it's NetBSD porting work status do not hesitate to e-mail me or the Milkymist mailing list :) I think FAGA based hardware needs setup of hardware, so NetBSD developer should write CPU softcore etc to FPGA chip. Maybe developers not familiar with this kind of works. For example, MilkyMist for DE0 namo is attractive for me. It is low price FPGA hardware. But I am completely newbie to FPGA device, and I cannot imagine what is needed to start MilkyMist on DE0 nano. You need: - The hardware - A Windows or Linux PC (don't know about BSD support, maybe with the linux syscall compatibility layer?) - The IDE for the FPGA vendor installed, for the DE0 it's the Altera IDE - Quartus II Web Edition Software (free of charge) - Clone the source code over there: https://github.com/Florent-Kermarrec/milkymist-ng-de0nano - Clone its dependencies (Migen and Mibuild from this github account: https://github.com/milkymist/) - Install Migen, Mibuild (python setup.py install, that's all) - cd milkymist-ng-de0nano make Then use whatever software your board needs to push the FPGA bitstream (the design file that tells the FPGA how to behave) in the FPGA. And there you are, you get a minimalistic Milkymist-ng system-on-chip with LatticeMico32 core, uart console, memory mapped GPIOs, SDRAM controller. A simple BIOS is provided, accessible from the UART. And I want to know performance information about FPGA board. I don't own this board, but you cannot seriously expect big fast FPGA for a very small amount of money. Those small dev boards usually feature the little children of the given FPGA family, which in some way is great because it's usually the only FPGAs supported by the Free of charge version of the IDE (this is true for Xilinx and Altera at least, dunno for Lattice or Actel) Microsoft Windows PC is needed? No Microsoft Windows PC needed, you can use only Linux if you want. For some boards however, it's only possible to push the bitstream (FPGA design file) to the board from Windows, only because sometimes there is no Linux software for that. That could be what decides you to buy a board and not to buy another.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On Sun, Sep 29, 2013 at 10:09:53AM +0900, Ryo ONODERA wrote: (21) Enable Firefox's WebRTC support Something is wrong and I cannot enable Firefox's WebRTC support. Problem is in SCTP (what is it?) code and libxul.so linking. SCTP = stream control transmission protocol, RFCs 4690, 3309, 2960. Think of it as an alternative to TCP for live video streams and the like. I have this on my TODO list (including evaluating wether adding SCTP supoort to the kernel would make more sense than the userland variant, IIUC firefox can be made to use both). Martin
Re: Various size of (Project) ideas for NetBSD and pkgsrc
The bit a about Hyper-V- all source is now part of FreeBSD-current tree following Microsoft policy changes few weeks ago, together with Citrix and NetApp. I tested the first alpha a few weeks ago and it seems to be working very well. The synthetic network adapter performance is the best I have tried so far. The SCSI adapter also works, as well as time sync, shutdown and heartbeat. Chavdar On 29 Sep 2013 02:09, Ryo ONODERA ryo...@yk.rim.or.jp wrote: Hi, I have (or have heard) some ideas for NetBSD and pkgsrc. Can someone add them to http://wiki.netbsd.org/projects/all-flat/ with good English and proper classification, if it seems ok? I cannot be mentor, because of lack of ability sadly. (1) Add UEFI boot support for NetBSD/amd64 I do not have newer PC, but I have heard newer PC uses UEFI to boot OSes instead of BIOS. Boot with UEFI should be added to NetBSD/amd64 (I do not know whether UEFI is available for i386 or not). I have seen EFI support option in Oracle VirtualBox. No newer PC may not be needed for development. (2) Create multiple packages from one pkgsrc package directory For example, pkgsrc/fonts/harfbuzz has icu option and theoretically non-icu part and icu part can be separate package, but splitting only icu part from harfbuzz is difficult in configure/build stage. In rpm (Red Hat package manager) case, build once and multiple packages is created is realized with custom do-install target. build once means reduce of build time. (3) Restore MIPS support for NetBSD 6 and current Sadly all my MIPS device is not usable with NetBSD 6 and current. If NetBSD 7 is released, NetBSD 5 support is dropped, and I cannot use supported NetBSD/mips on any MIPS hardware. In this case, I have spare NetBSD/cobalt machine (Cobalt raq), and I can send it to project worker worldwide. (4) Add OSS4 support to NetBSD I want to use newer wine (pkgsrc/emulators/wine). But according to pkgsrc/doc/TODO, OSS3 support is dropped and I cannot use newer wine anymore. Adding OSS4 support makes me happy. (5) Add XFS support to NetBSD I have heard Red Hat Enterprise Linux will use XFS as standard filesystem. Accessing Linux's filesystem is useful and important feature. At least I am not sticky to BSD licensed version. I feel treating like ZFS is good idea. (6) Porting Chromium web browser to NetBSD I have not tested build of Chromium (open source edition of Google Chrome), and I have a few experience about Google Chrome. Chromium may be useful web browser for NetBSD. (7) Apache OpenOffice for NetBSD I have completely no idea about Apache OpenOffice. It may be one of the most important application. (8) Porting NetBSD to some FPGA CPU board OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is available for FPGA board. At least OpenRISC 1200 and MicroBlaze have Linux support. Supporting these architecture is interesting for NetBSD. (I have no idea about NetBSD/nios2 status.) (9) Add Microsoft's Hyper-V support to NetBSD There is two types of Hyper-V, Windows Server 2012's Hyper-V and Windows Server 2012R2's Hyper-V. I have heard Windows Server 2012's Hyper-V is supported on FreeBSD. But I cannot find the code for it. Similar to NetBSD/azure? http://wiki.netbsd.org/projects/project/netbsd_on_microsoft_azure/ (10) Porting Broadcom's brcmfmac and brcmsmac WiFi driver to NetBSD brcmfmac and brcmsmac are ISC licensed Linux driver for Broadcom's WiFi adapter. My MacBook Air mid 2012 has brcmfmac or brcmsmac device. Supporting the device makes me happy. Web page is in 500 - Internal Server Error now sadly. http://wireless.kernel.org/en/users/Drivers/brcm80211 (11) Improve NetBSD/evbearm support As you know, NetBSD/evbearm has some problems. http://gnats.netbsd.org/48130 , for Kirkwood http://gnats.netbsd.org/48193 and http://gnats.netbsd.org/48215 for pkg_add (14) commit mail of www.pkgsrc.org wiki I have heard some difficulties, but I do not know it in detail. (15) user-editable wiki site If wiki.NetBSD.org is not suitable for this purpose. Different URL (even non-NetBSD.org domain name) should be considered. (16) Updating compat_linux I cannot run firefox's Linux binary with compat_linux. (17) DTrace's syscall provider I cannot test riz@'s DTrace syscall provider patch. But syscall provider support should be added to NetBSD. (18) Porting valgrind to NetBSD I have heard only old version is available. (19) Support some Linux infrastructure that is used by Gnome systemd or other mechanism is used by Gnome related software. I do not know much about them, but sometimes I encounter systemd or similar mechanism are not found error when creating pkgsrc packages. I am discouraged with the error. (20) Add inotify interface to NetBSD Some software that targets Linux use inotify, I have heard *BSD has kqueue support and it should be used. But implementing Linux compatible inotify with kqueue or similar is useful for using
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On 09/28/2013 08:09 PM, Ryo ONODERA wrote: (3) Restore MIPS support for NetBSD 6 and current Sadly all my MIPS device is not usable with NetBSD 6 and current. If NetBSD 7 is released, NetBSD 5 support is dropped, and I cannot use supported NetBSD/mips on any MIPS hardware. In this case, I have spare NetBSD/cobalt machine (Cobalt raq), and I can send it to project worker worldwide. Just my $.02 worth... I have several Cobalt units - one of which I'm going to be loading with NetBSD 5 on a CF card here as soon as the card shows up in the mailbox. The issue here as I see it is there is a limited number of these boxes and they aren't making any more of them. And even with NetBSD these boxes are getting comparatively slower every year while kernels and such get bigger every year. Personally even as a NetBSD Cobalt user, and happy, I can see where the effort to keep those in the tree might be not worth it overall. That said I too would like them to keep it in there too just for security reasons but since those boxes are often giving way to VMs that eat less and are current I just don't see it happening. But I've been wrong before. :-) -- What? Me worry?
Re: Various size of (Project) ideas for NetBSD and pkgsrc
Hi, From: matthew sporleder msporle...@gmail.com, Date: Sun, 29 Sep 2013 13:41:55 -0400 I have noted some places where you might find similar projects. Also you should not feel intimidated to add these yourself to the wiki. It's very easy to fix spellings, etc, as needed. It's more difficult to express your ideas beyond how you state them. :) The project template is very easy to use! Thanks for your links. I feel that some ideas may not be relevant to http://wiki.netbsd.org/projects/ . How do you think threshold of adding ideas to projects wiki page? Thank you. -- Ryo ONODERA // ryo...@yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
Re: Various size of (Project) ideas for NetBSD and pkgsrc
Hi, From: Yann Sionneau yann.sionn...@gmail.com, Date: Sun, 29 Sep 2013 19:37:14 +0200 Hi Ryo, Le 29/09/13 03:09, Ryo ONODERA a écrit : Hi, (8) Porting NetBSD to some FPGA CPU board OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is available for FPGA board. At least OpenRISC 1200 and MicroBlaze have Linux support. Supporting these architecture is interesting for NetBSD. (I have no idea about NetBSD/nios2 status.) I am in the process of adding support for LatticeMico32 (LM32) architecture to NetBSD 6 kernel. Last year a MMU (memory management unit) has been added to the LM32 softcore which makes it able to run Linux or NetBSD. LM32 already had a uCLinux (noMMU) working port. This year I started the project to port NetBSD 6 kernel on MMU-enabled LM32 CPU in general and on the Milkymist open source System-on-Chip in particular. Today I had my first result on this project: http://pastebin.com/MJgB6Y05 - NetBSD 6 kernel immediately panics and dies. Even though this might - seem like a poor result, there have been a lot of work behind it. This is a first step which looks very promising :) (at least console driver works ;)) Great work! I am not kernel developer, but I want to know the following questions. How about status of NetBSD current? According to NetBSD development process, porting to current is essential, if I understand correctly. And how about bus support? According to MiklyMist wiki, MilkyMist uses wishbone like bus, and I understand correctly, wishbone or similar bus support are not implemented in current NetBSD. The Milkymist System-on-Chip runs on various FPGAs (Spartan 3, Spartan 6, Virtex 4 etc) from various FPGA vendors (Xilinx, Lattice, Altera) It has been ported on numerous boards (Milkymist One, ML401, De0-nano, Nexys3 etc...) It uses LatticeMico32 (open source softcore) as it's CPU softcore. If you want more information about Milkymist and it's NetBSD porting work status do not hesitate to e-mail me or the Milkymist mailing list :) I think FAGA based hardware needs setup of hardware, so NetBSD developer should write CPU softcore etc to FPGA chip. Maybe developers not familiar with this kind of works. For example, MilkyMist for DE0 namo is attractive for me. It is low price FPGA hardware. But I am completely newbie to FPGA device, and I cannot imagine what is needed to start MilkyMist on DE0 nano. And I want to know performance information about FPGA board. Microsoft Windows PC is needed? Additional hardware? Writing how to setup hardware is needed, and it may be another NetBSD project idea or homework for MilkyMist people. By the way, what is your target? MilkyMist SoC? MilkyMist-ng? And How to get the hardware that is exactly as same as yours? This question is how to start NetBSD/milkymist question. What hardware/software should I buy to follow your work? And I have noticed some open source SPARC CPU sotfcore is available for FPGA board (T1, S1, LEON, etc.). FYI MicroBlaze CPU is not open source, even though there are a few open source clones out there (aeMB and others) Nios II is not open source neither. OpenRISC is open source and has a MMU and a Linux port, it's a nice project as well :) I am not sticky to open source hardware. Of course, if CPU softcore is open source, I am more happy. And do not forget NetBSD/emips. All of this being said, I agree with you that having NetBSD running on FPGA would be a really cool achievement, especially on OpenSource hardware (PCB and FPGA design) which allows for deep understanding of hardware, digital design and low level software as well as tweaking the CPU (cache size, TLB size, instructions, pipeline configuration etc). Thanks for your information. I think the following idea is shown in this thread by you and me. (a) Porting NetBSD to MilkyMist SoC/MilkyMist-ng open source hardware (status: in progress) (b) Porting NetBSD to OpenRISC 1200 (target board is not specified) (c) Porting NetBSD to MIcroBlaze (target board is not specified) (d) Porting NetBSD to FPGA board with SPARC CPU softcore (target CPU and board is not specified) (e) Writing how to start NetBSD/milkymist with a certain board (target board should be specified) Thank you. -- Ryo ONODERA // ryo...@yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
Re: Various size of (Project) ideas for NetBSD and pkgsrc
I have heard that disabling DEBUG option(s) in RPI kernel config file improves performance issue. But I have not compared debug kernel and non-debug kernel. Thanks for the information. I will try that. It sounds promising. --Benny.
Re: Various size of (Project) ideas for NetBSD and pkgsrc
From: Martin Husemann mar...@duskware.de, Date: Sun, 29 Sep 2013 10:22:05 +0200 On Sun, Sep 29, 2013 at 10:09:53AM +0900, Ryo ONODERA wrote: (21) Enable Firefox's WebRTC support Something is wrong and I cannot enable Firefox's WebRTC support. Problem is in SCTP (what is it?) code and libxul.so linking. SCTP = stream control transmission protocol, RFCs 4690, 3309, 2960. Think of it as an alternative to TCP for live video streams and the like. I have this on my TODO list (including evaluating wether adding SCTP supoort to the kernel would make more sense than the userland variant, IIUC firefox can be made to use both). After SCTP support is improved, I will try to enable Firefox WebRTC support again. Thank you. -- Ryo ONODERA // ryo...@yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
Re: Various size of (Project) ideas for NetBSD and pkgsrc
On Sun, Sep 29, 2013 at 1:58 PM, Ryo ONODERA ryo...@yk.rim.or.jp wrote: Hi, From: matthew sporleder msporle...@gmail.com, Date: Sun, 29 Sep 2013 13:41:55 -0400 I have noted some places where you might find similar projects. Also you should not feel intimidated to add these yourself to the wiki. It's very easy to fix spellings, etc, as needed. It's more difficult to express your ideas beyond how you state them. :) The project template is very easy to use! Thanks for your links. I feel that some ideas may not be relevant to http://wiki.netbsd.org/projects/ . How do you think threshold of adding ideas to projects wiki page? Thank you. -- Ryo ONODERA // ryo...@yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3 As I read it, projects are enhancements and new ideas. Fixes, on the other hand, are fixes. :) In your case the broken MIPS stuff seems out of scope for the projects page even though it is likely a large project in the sense that it requires a lot of work. I'm not the gatekeeper, but that's how I see the current projects page.
Various size of (Project) ideas for NetBSD and pkgsrc
Hi, I have (or have heard) some ideas for NetBSD and pkgsrc. Can someone add them to http://wiki.netbsd.org/projects/all-flat/ with good English and proper classification, if it seems ok? I cannot be mentor, because of lack of ability sadly. (1) Add UEFI boot support for NetBSD/amd64 I do not have newer PC, but I have heard newer PC uses UEFI to boot OSes instead of BIOS. Boot with UEFI should be added to NetBSD/amd64 (I do not know whether UEFI is available for i386 or not). I have seen EFI support option in Oracle VirtualBox. No newer PC may not be needed for development. (2) Create multiple packages from one pkgsrc package directory For example, pkgsrc/fonts/harfbuzz has icu option and theoretically non-icu part and icu part can be separate package, but splitting only icu part from harfbuzz is difficult in configure/build stage. In rpm (Red Hat package manager) case, build once and multiple packages is created is realized with custom do-install target. build once means reduce of build time. (3) Restore MIPS support for NetBSD 6 and current Sadly all my MIPS device is not usable with NetBSD 6 and current. If NetBSD 7 is released, NetBSD 5 support is dropped, and I cannot use supported NetBSD/mips on any MIPS hardware. In this case, I have spare NetBSD/cobalt machine (Cobalt raq), and I can send it to project worker worldwide. (4) Add OSS4 support to NetBSD I want to use newer wine (pkgsrc/emulators/wine). But according to pkgsrc/doc/TODO, OSS3 support is dropped and I cannot use newer wine anymore. Adding OSS4 support makes me happy. (5) Add XFS support to NetBSD I have heard Red Hat Enterprise Linux will use XFS as standard filesystem. Accessing Linux's filesystem is useful and important feature. At least I am not sticky to BSD licensed version. I feel treating like ZFS is good idea. (6) Porting Chromium web browser to NetBSD I have not tested build of Chromium (open source edition of Google Chrome), and I have a few experience about Google Chrome. Chromium may be useful web browser for NetBSD. (7) Apache OpenOffice for NetBSD I have completely no idea about Apache OpenOffice. It may be one of the most important application. (8) Porting NetBSD to some FPGA CPU board OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is available for FPGA board. At least OpenRISC 1200 and MicroBlaze have Linux support. Supporting these architecture is interesting for NetBSD. (I have no idea about NetBSD/nios2 status.) (9) Add Microsoft's Hyper-V support to NetBSD There is two types of Hyper-V, Windows Server 2012's Hyper-V and Windows Server 2012R2's Hyper-V. I have heard Windows Server 2012's Hyper-V is supported on FreeBSD. But I cannot find the code for it. Similar to NetBSD/azure? http://wiki.netbsd.org/projects/project/netbsd_on_microsoft_azure/ (10) Porting Broadcom's brcmfmac and brcmsmac WiFi driver to NetBSD brcmfmac and brcmsmac are ISC licensed Linux driver for Broadcom's WiFi adapter. My MacBook Air mid 2012 has brcmfmac or brcmsmac device. Supporting the device makes me happy. Web page is in 500 - Internal Server Error now sadly. http://wireless.kernel.org/en/users/Drivers/brcm80211 (11) Improve NetBSD/evbearm support As you know, NetBSD/evbearm has some problems. http://gnats.netbsd.org/48130 , for Kirkwood http://gnats.netbsd.org/48193 and http://gnats.netbsd.org/48215 for pkg_add (14) commit mail of www.pkgsrc.org wiki I have heard some difficulties, but I do not know it in detail. (15) user-editable wiki site If wiki.NetBSD.org is not suitable for this purpose. Different URL (even non-NetBSD.org domain name) should be considered. (16) Updating compat_linux I cannot run firefox's Linux binary with compat_linux. (17) DTrace's syscall provider I cannot test riz@'s DTrace syscall provider patch. But syscall provider support should be added to NetBSD. (18) Porting valgrind to NetBSD I have heard only old version is available. (19) Support some Linux infrastructure that is used by Gnome systemd or other mechanism is used by Gnome related software. I do not know much about them, but sometimes I encounter systemd or similar mechanism are not found error when creating pkgsrc packages. I am discouraged with the error. (20) Add inotify interface to NetBSD Some software that targets Linux use inotify, I have heard *BSD has kqueue support and it should be used. But implementing Linux compatible inotify with kqueue or similar is useful for using some software on NetBSD. (21) Enable Firefox's WebRTC support Something is wrong and I cannot enable Firefox's WebRTC support. Problem is in SCTP (what is it?) code and libxul.so linking. (22) Creating better conversion tool for CVS to anywhere Joerg's src and pkgsrc repositories on github is great, but it seems that it has no tags. His tool is not sufficient for moving from CVS to somewhere. (23) Lua support for kernel and userland Lua is imported to NetBSD base, but nothing uses it. And update is not done. Lua kernel support should be
