Jerone Young wrote:
>> I don't really see why we need to keep the top-level directory small. >> > > I think it's more of a personal thing. Mainly do it for anyone who is > getting into the project for the first time. Once you've been doing it > for a while it's no issue.. but first time your trying to figure out > what is "vgabios" and is it related to kvm .. well it's actually more > related to qemu (which kvm happens to use)... cases like that .. but > really it's not a big deal .. just figured I'd see what folks thought > about the idea. > > Maybe a README.dev can help the first-timers. I'm concerned about the old-timers' tab key. >> However, why do we need libfdt? Is it not carried by distros, or do you >> need to make changes? >> > > Well it actually isn't distributed with each distro .. sigh .. actually > this comes from a tool called dtc, compiles/decompiles a device tree. > Even the linux kernel has it's own version of libfdt ... so it's not > exactly a central coordinated effort. It's something that kind of gets > passed from project to project but never stand alone. So we kind of have > to do the same Okay. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
